Closed Anomander closed 9 months ago
This is due to pod-identity-webhook using an outdated k8s client before the restartPolicy
field was added to Containers
type.
Have a fix here: https://github.com/aws/amazon-eks-pod-identity-webhook/pull/209
I investigated the issue as well, and came to the same conclusion regarding the source of the bug and fix to bring. We opened a ticket on AWS support side, and suggested it to bring it up here. It's currently making the SideCar feature unusable and it would be great to have that added to EKS asap 🙏
Is there an expected date and time for the distribution of this solution to #209
Im on the latest version of eks on both the cluster and nodes and this is still happening.
Change is available in EKS, marking this as closed.
@prateekgogia To which version I need to upgrade in-order to have the fix? Currently experiencing this issue with k8s 1.29 with eks.17
What happened: With the release of 1.29 the new Sidecars feature is available. The feature introduces the new field in the container definition that can mark some init containers as non-blocking and running perpetually.
The mutating webhook removes the new field from containers, preventing the new feature from being used.
What you expected to happen: Sidecars are updated with IRSA, but remain functional
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: Here's the log of the mutation being applied, note the absence of the
restartPolicy
in the patch.Environment:
aws eks describe-cluster --name <name> --query cluster.platformVersion
): "eks.1"aws eks describe-cluster --name <name> --query cluster.version
): "1.29"