You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of our pods should assume a specific AWS role and we are configuring it via service account annotation. After eks cluster upgrade the mutation of the pod stopped working and it had only a default node group role.
I changed the mutatingwebhookconfigurations policy from Ignore to Fail for pod-identity-webhook under the cluster and after that pod failed to start with the error
What happened:
One of our pods should assume a specific AWS role and we are configuring it via service account annotation. After eks cluster upgrade the mutation of the pod stopped working and it had only a default node group role.
I changed the
mutatingwebhookconfigurations
policy from Ignore to Fail forpod-identity-webhook
under the cluster and after that pod failed to start with the errorAfter some additional investigation, I found that the problem solved once I change
to
IIUC the problem that mutation webhook handler is using deprecated version of admission API
v1beta1
when it should usev1
What you expected to happen:
The mutation of the pod should work without any errors.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
):eks.15
aws eks describe-cluster --name <name> --query cluster.version
): 1.27The text was updated successfully, but these errors were encountered: