-
Notifications
You must be signed in to change notification settings - Fork 922
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
kubectl patch initContainers image doesn't work #27
Comments
After debugging a bit, |
Thanks. Should I close this and open a feature request to the apiserver to ask if the initContainer can be changed? |
I believe kubernetes/kubernetes#47264 is an issue with same root cause that filed against main repo. |
Is this a request for help? : Nope
What keywords did you search in Kubernetes issues before filing this one? : "patch"
Is this a BUG REPORT or FEATURE REQUEST? : BUG REPORT?
Kubernetes version (use
kubectl version
): v1.6.2Environment:
What happened:
I have a pod that contains nginx and php-fpm containers that need to reference the same sourcecode. To do this I use a
initContainers
to copy some sourcecode to aemptyDir
volume. It works nicely.To deploy a new version of the app, the only thing that needs changing is the image of the container in the initContainers. I would like to be able to patch it like this:
It returns:
but checking with
kubectl get deployment thedeployment -o json | less
shows it's not the case.What you expected to happen:
The deployment should be updated with a the new image. (and a new deployment triggered)
How to reproduce it :
Try to patch the image to change from
busybox:latest
tobusybox:1.25
:Even though it says it's patched, check busybox image in the deployment to see it's not changed with:
The text was updated successfully, but these errors were encountered: