Results 4 comments of Thiago Mello

Another workaround - which is a bit more radical than the one proposed above - is to instead of using the EKS Pod Identity (`eks.amazonaws.com/role-arn`) with a service account -...

Was having the same issue until I solved it by adding an alias to the provider and referencing it in the resource: ``` provider "grafana" { alias = "bare-metal"