This message was deleted.

kubernetes.

are you expecting pulumi to go through the api server right?

If you are using the

pulumi/eks

package, then it will attempt to connect to the EKS control plane to provision some additional EKS specific resources and if the pulumi client is unable to connect to the control plane, it can result in an error like you're getting.

I was expecting that pulumi will call kubernetes api to create and watch ressources.

Are you using

pulumi/kubernetes

then?

yes

I see. Then yes, in that case the pulumi client will communicate with your Kubernetes control plane to provision and manage k8s resources. That error is not "normal" in that assuming your cluster is functional and reachable, I would not expect you to get that error. It seems like that might be an error from "inside" Kubernetes though where it's trying to dispatch something to a node and failing, so might not be specific to Pulumi.

but why pulumi is connecting to the kubelet instead of the kube api?

I'm not sure it is. I think that error is being returned from the kube api itself. What endpoint is defined in your kubeconfig?

I can try to get those. Sorry I forgot to check that workspace before leaving work yesterday