not sure if this is the right spot but - we’re usi...
# kubernetes
f
not sure if this is the right spot but - we’re using
pulumi_eks
and in modifying an existing cluster’s
VpcCniOptionsArgs
, we’re getting this message in CI/CD (which we’ve never needed
kubectl
to run)
Copy code
Diagnostics:
  eks:index:VpcCni (cluster-name):
    error: Could not set VPC CNI options: kubectl is missing. See <https://kubernetes.io/docs/tasks/tools/install-kubectl/#install-kubectl> for installation instructions.
does anyone know what we might be missing (other than installing kubectl in our remote runners, which seems wrong to do)
b
The EKS provider uses kubectl, you'll need to install it. It's the only way patch resources in EKS unfortunately
(We are actively working on fixing this, but for now you'll need kubectl)
f
ah got it. glad im not missing anything super obvious. thank you!