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
Unable to update cronjob image using kubectl set image #57393
Comments
I have found the following way to update the image;
Still it would be nice to use the same tool (kubectl set image) for both deployments and cronjobs. |
/sig cli |
yeap, the |
👍 |
Fixed in #57742 |
Which version will contain the new kubectl set image support for cronjobs? Is this just a command line patch or also system images? |
@richtera, it's in v1.10. Seem to be just a command line patch. This worked for me: I know this is an older thread but hopefully it helps someone else! |
@calebmcelroy oh cool. Thanks I'll be able to fix my scripts and simplify things |
what is exactly the cronjobmetadataname here |
/kind feature
What happened:
I would like to use a newer version of my image in a cronjob, but I can't update the cronjob template using 'kubectl set'
What you expected to happen:
I would expect to issue a command like the following, but it's not possible to update a cronjob template.
How to reproduce it (as minimally and precisely as possible):
create a cronjob and try to update the image that is pulled for each job.
Environment:
Kubernetes version (use
kubectl version
):Client Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.5", GitCommit:"cce11c6a185279d037023e02ac5249e14daa22bf", GitTreeState:"clean", BuildDate:"2017-12-07T16:16:03Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"8", GitVersion:"v1.8.4", GitCommit:"9befc2b8928a9426501d3bf62f72849d5cbcd5a3", GitTreeState:"clean", BuildDate:"2017-11-20T05:17:43Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Cloud provider or hardware configuration:
azure
Install tools:
acs-engine
The text was updated successfully, but these errors were encountered: