This message was deleted.
# general
s
This message was deleted.
c
are you perhaps using the default k8s provider (i.e. not creating an explicit provider based on the eks cluster you just created)? if you don’t specify the k8s provider, pulumi may be trying to use your default “kubeconfig” (which may or may not be set) and thus try to install a helm chart on a nonexistent cluster. if you create an explicit kubernetes provider based on the eks cluster you just created, it 1) won’t try to deploy the helm chart before the eks cluster is up, and 2) deploy the helm chart in the correct cluster
a
ok so I have - I think - done what you suggest. The helm chart resource now has a block
Copy code
{ provider: cluster.provider }
I am trying to forget the bit where I had to use a perl oneliner to convert the output of the ``pulumi stack --show-urns`` to a string that pulumi state delete would take
i have managed to convince the state that the old cluster and objects in it do not exist and I am now trying to run a full test
c
you may already know this, but it is worth noting that the eks cluster isn’t fully realized until
pulumi up
is run. so unless you will export the kubeconfig (or some other output of the eks cluster) and use it in a separate project for your helm charts, you’ll want to run an Apply function to set the kubernetes provider. I find using the the kubeconfig from the eks cluster output to create the kubernetes provider simplest
a
i have local.run( { command:`aws eks update-kubeconfig --region ${config.region} --name ${c1}` }, {}); to set up the local .kube/config
c
did that work for you? unless you are running the helm chart in a separate project after the eks project is run, i don’t think pulumi will set the default kubernetes provider to the newly created cluster that way. others may have a better method, but i would suggest creating the provider in code after the cluster creation and use that to install helm charts. for reference, you can view these docs: inputs and outputs / apply function: https://www.pulumi.com/docs/intro/concepts/inputs-outputs/ kubernetes provider: https://www.pulumi.com/registry/packages/kubernetes/api-docs/provider/ pulumi examples (search for an eks example for your language): https://github.com/pulumi/examples
b
@adamant-waitress-42469 been following the scrollback, did you get everything unstuck?
a
Yeah, all unjammed after a couple of hours of toil. Of course EKS then played hard to get...