-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
Update nvidia-gpu-device-plugin to apps/v1 and use RollingUpdate updateStrategy. #64296
Update nvidia-gpu-device-plugin to apps/v1 and use RollingUpdate updateStrategy. #64296
Conversation
…teStrategy. Even though RollingUpdate is the default updateStrategy, we need to specify it explicitly here because otherwise updating from extensions/v1beta1 to apps/v1 doesn't change the updateStrategy.
/lgtm |
/lgtm |
/assign @roberthbailey |
/test pull-kubernetes-e2e-gke-device-plugin-gpu |
/retest |
/lgtm |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, jiayingz, mindprince, roberthbailey, vishh 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 |
We need to cherrypick this change to 1.9 and 1.10, right? |
Only to 1.10 |
/test pull-kubernetes-kubemark-e2e-gce-big |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
@mindprince: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
I think this broke all the node e2e jobs: |
@mindprince is ooo. I will submit a fix PR to modify DsFromManifest() to use &apps.DeamonSet{}. |
Curious why it wasn't caught by pull-kubernetes-node-e2e. |
Because https://raw.githubusercontent.com/kubernetes/kubernetes/master/cluster/addons/device-plugins/nvidia-gpu/daemonset.yaml wouldn't be updated until the PR was merged. Given that, wouldn't changes like this affect all branches? |
Ah right. Now I remember. The 1.8 and 1.10 branches are using the yaml config from their own branches, but we seem to forget to update 1.9. I will submit a PR to update 1.9. |
This seems a bit fragile :-( |
I know :(. Would be better to just retrieve the yaml from current source, if we can figure out how to do this... |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Fix DsFromManifest() after we switch from extensions/v1beta1 to apps/v1 in cluster/addons/device-plugins/nvidia-gpu/daemonset.yaml. **What this PR does / why we need it**: Fixes broken node e2e jobs caused by #64296. **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes # **Special notes for your reviewer**: **Release note**: ```release-note ```
#64340-#64404-upstream-release-1.10 Automatic merge from submit-queue. Automated cherry pick of #64296: Update nvidia-gpu-device-plugin to apps/v1 and use #64340: Fix DsFromManifest() after we switch from extensions/v1beta1 #64404: DaemonSet internals are still in extensions Cherry pick of #64296 #64340 #64404 on release-1.10. #64296: Update nvidia-gpu-device-plugin to apps/v1 and use #64340: Fix DsFromManifest() after we switch from extensions/v1beta1 #64404: DaemonSet internals are still in extensions ```release-note Fix nvidia-gpu-device-plugin DaemonSet config to ensure correct device plugin upgrade ```
Even though RollingUpdate is the default updateStrategy, we need to
specify it explicitly here because otherwise updating from
extensions/v1beta1 to apps/v1 doesn't change the updateStrategy.
Related to #57125 and #63634
/assign @vishh @jiayingz
/cc @janetkuo