-
Notifications
You must be signed in to change notification settings - Fork 38.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
Deprecate kubelet "enable-controller-attach-detach" option #55517
Comments
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
according to #20262,
I think we can remove the logic for kubelet doing the attach/detach. |
It's lengthy process to deprecate something. https://kubernetes.io/docs/reference/using-api/deprecation-policy/ With the old policy (when we introduced the annotation), it would fall into
But with the new one, it seems impossible to remove the annotation:
Could we get an exception in this case? |
Discussed with @saad-ali a little, he says there are users that still need this flag so I'm not sure if we can ever remove it. If we cannot remove it and need to support it forever, then maybe we need to at least document the limitations of using this, and test this configuration as well. |
I think this flag is still needed at least for attach/detach operations in case when some static pod needs volume and controller isn't up yet. My case is to use cinder volume plugin in static pod definition like follows.
|
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/reopen |
@msau42: Reopened this issue. In response to this:
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. |
This is an untested configuration and as we're adding more features and designing around AD controller/kubelet coordination for things like migration, this functionality is bound to get broken. We should think about how to support the static pod scenario outlined above considering the move towards CSI and eventually removing all in-tree plugin code. Many CSI features today depend on K8s api objects and won't work in a static pod/master bootstrapping scenario. |
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
@kubernetes/sig-storage-feature-requests
What happened:
Are there any use cases where we still need to support kubelet doing the attach/detach? If not, let's deprecate this field and eventually remove it.
The text was updated successfully, but these errors were encountered: