eksctl update addon
with version: latest
and useDefaultPodIdentityAssociations
fails
#7841
Labels
area/podidentity
kind/bug
priority/important-longterm
Important over the long term, but may not be currently staffed and/or may require multiple releases
From a user on Slack:
eksctl update addon
fails for this config file:2024-06-18 13:45:07 [ℹ] Kubernetes version "1.28" in use by cluster "cluster-79"
2024-06-18 13:45:08 [ℹ] no new version provided, preserving existing version: v1.2.0-eksbuild.1
2024-06-18 13:45:08 [ℹ] updating addon
2024-06-18 13:45:19 [ℹ] addon "eks-pod-identity-agent" active
2024-06-18 13:45:20 [ℹ] no new version provided, preserving existing version: v1.31.0-eksbuild.1
2024-06-18 13:45:21 [ℹ] updating IAM resources stack "eksctl-cluster-79-addon-aws-ebs-csi-driver-podidentityrole-ebs-csi-controller-sa" for pod identity association "a-xpaah4j4xsvt9af6l"
2024-06-18 13:45:22 [ℹ] waiting for CloudFormation changeset "eksctl-kube-system-ebs-csi-controller-sa-update-1718714721" for stack "eksctl-cluster-79-addon-aws-ebs-csi-driver-podidentityrole-ebs-csi-controller-sa"
2024-06-18 13:45:22 [ℹ] nothing to update
2024-06-18 13:45:22 [ℹ] IAM resources for kube-system/ebs-csi-controller-sa (pod identity association ID: a-xpaah4j4xsvt9af6l) are already up-to-date
2024-06-18 13:45:22 [ℹ] updating addon
2024-06-18 13:46:04 [ℹ] addon "aws-ebs-csi-driver" active
Error: getting recommended policies for addon vpc-cni
eksctl needs to resolve the keyword
latest
to the latest version before attempting to describe recommended policies for an addon.The text was updated successfully, but these errors were encountered: