-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Readiness Gate Injection Breaks Kubernetes 1.29 Sidecar Pods #3649
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
was able to replicate the same using above steps AWS Load Balancer controller version: v2.8.0 |
Thanks for the reporting, we are working on upgrading the controller-runtime to latest version, and k8s deps to v0.30.0, which should fix this issue: #3707 |
yes And I see the following in AWS LBC pods logs when i enable debug logs
|
@jlrgraham23, @kakarotbyte hi thanks for the patience |
Describe the bug
When the pod readiness gate feature is enabled on a namespace in a Kubernetes 1.29 cluster it strips away the
restartPolicy: Always
values on containers in theinitContainers
block; this effectively breaks the new SideCar Containers feature in 1.29.This looks to be due to use of an older version of the
k8s.io/api
library here:https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/go.mod#L22C2-L22C20
Same issue here with the EKS specific Pod Identity Webhook.
Upstream docs: https://kubernetes.io/blog/2023/08/25/native-sidecar-containers/
Steps to reproduce
elbv2.k8s.aws/pod-readiness-gate-inject=enabled
label.restartPolicy: Always
on an init container in a pod.Inspecting the resulting pods from this Deployment shows that the
restartPolicy
attribute has been removed in flight.Expected outcome
The readiness gate should not remove the
restartPolicy
attribute from containers in theinitContainers
spec.Environment
The text was updated successfully, but these errors were encountered: