-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[RFE] Support pod selector in drain options #40003
Comments
|
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions. |
Not stale. Now implement in the controller, needs to be used in Rancher. |
This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions. |
Is your feature request related to a problem? Please describe.
Longhorn doc advises that users should drain a node with
--pod-selector='app!=csi-attacher,app!=csi-provisioner'
. But the pod selector is not supported in drain options. Harvester relies on Rancher to upgrade the underlying RKE2 stack and would like to have this feature.Describe the solution you'd like
Support passing pod selector (same as
kubectl drain --pod-selector
) when draining a node.Describe alternatives you've considered
I can't find a workaround.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: