No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

Code:
```export function createCloudwatchMetricsResources(
  cluster: eks.Cluster,
  clusterName: string
) {
  const awsRegion = aws.getRegion().name;
  const cloudwatchConfig = new k8s.yaml.ConfigGroup(
    "cloudwatch",
    {
      files: "cwagent/*.yaml",
      transformations: [
        (obj: any) =&gt; {
          // Transform the YAML to set the cluster and region names
          if (
            obj.kind === "ConfigMap" &amp;&amp;
            obj.metadata.name === "cwagentconfig"
          ) {
            obj.data["cwagentconfig.json"] = obj.data["cwagentconfig.json"]
              .replace(/{{cluster_name}}/g, clusterName)
              .replace(/{{region_name}}/g, awsRegion);
          }
        }
      ]
    },
    { providers: { kubernetes: cluster.provider } }
  );
}```

How are you providing your `kubeconfig`? It seems like Pulumi isn't finding it.

Hmm I'm not sure exactly.  This is in the same program where we create the cluster and export the kubeconfig like
```export const eksClusterKubeconfig = eksCluster.kubeconfig;```

Should I be making a new provider based on that config, or just using `cluster.provider`

You're using `@pulumi/eks` and `cluster.provider` is coming from there?

Are you using assume role with AWS? If so, you might need to set your AWS credentials differently per <https://github.com/pulumi/pulumi-eks/issues/140>.

yes we are using assume role.  From reading that, I presume you are suggeasting we need to add a `CreationRoleProvider`  to the cluster creation?

Maybe a dumb question: I understand which role to pass in, but which `provider`  goes into the `CreationRoleProvider`?

so it seems that pulumi doesn't like adding that to a previously created cluster.  When running `up`  I get this error:

``` aws:eks:Cluster (eks-cluster-eksCluster):
    error: error creating EKS Cluster (infra-test): ResourceInUseException: Cluster already exists with name: infra-test
    {
      ClusterName: "infra-test",
      Message_: "Cluster already exists with name: infra-test"
    }```

is there a workaround other than `destroy`  ?

A destroy followed by an up worked!  Thanks so much.  Are there any follow up items needed here on your end?  Any way to make this more obvious in the error message and/or documentation?

I opened <https://github.com/pulumi/docs/issues/2637> to better document this. Please add any additional thoughts to that if you have them on how this could be better documented.