-
Notifications
You must be signed in to change notification settings - Fork 2k
Add Deployment rollout restart example #2116
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
Conversation
|
Welcome @ddubson! |
/assign @yue9944882 |
AppsV1Api appsV1Api = new AppsV1Api(client); | ||
|
||
String deploymentName = "example-nginx"; | ||
String imageName = "nginx:latest"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fwiw, using the latest
tag is an anti-pattern maybe make this a specific semantic version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏼 Thanks for catching that! I applied a specific tag 1.21.6
instead of latest
.
Thanks for the PR! One minor nit, otherwise LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
plz run the formatter mvn spotless:apply
, otherwise LGTM
@yue9944882 ah I was looking for the style formatter, thanks for guiding me to it. I applied it and re-pushed my changes. |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: brendandburns, ddubson The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This is a client-java v15.x compatible example of a Deployment resource rollout restart function which involves several indirect/non-trivial steps, which I thought could be quite useful for anyone seeking to have greater programmatic control over their Kubernetes deployments.