Hey folks. I'm using pulumi to deploy helm charts into my GKE cluster but for whatever reason, the admin kubeconfig isn't consistently used. I'll need to sign in with my own gcloud get-credentials, type my password, etc. before pulumi will work. This also means running pulumi in github actions is just downright broken. I'm using the gcp-py-gke example exactly but the workflow seems broken. Hopefully I'm just doing something a little bit wrong. Any advices? (cc @Tyler Hayden)

Getting a lot of warnings now when I spin up an EKS cluster using the Pulumi EKS Cluster API. The warnings look like this:

Warning: resource customresourcedefinitions/eniconfigs.crd.k8s.amazonaws.com is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
Warning: resource customresourcedefinitions/policyendpoints.networking.k8s.aws is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.

Is there some argument to

eks.Cluster

that resolves this? Thanks.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.

This message was deleted.