-
Notifications
You must be signed in to change notification settings - Fork 1.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
Improve API around machine deletion strategy #7021
Comments
cc @vincepri |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/lifecycle frozen |
@fabriziopandini: GuidelinesPlease ensure that the issue body includes answers to the following questions:
For more details on the requirements of such an issue, please see here and ensure that they are met. If this request no longer meets these requirements, the label can be removed 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 issue has not been updated in over 1 year, and should be re-triaged. You can:
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/ /remove-triage accepted |
/priority important-longterm |
just waiting for the next API version to be cut |
User Story
As a user, I would like to have a clean and simple API for configuring machine deletion strategy
Detailed Description
In recent version we expanded MachineSpec with fields allowing us to configure machine deletion strategy,
nodeDeletionTimeout
,nodeDrainTimeout
and alsovolumeDetachTimeout
(#6413); there are also annotations allowing to enable/disable one of the machine deletion steps, like e.gmachine.cluster.x-k8s.io/exclude-node-draining
Last but not least we have more requests in the pipeline, like e.g. the request for adding support for DaemonSet eviction when draining nodes
This ticket is about discussing how to normalize the API surface for machine deletion strategy by (some ideas):
/kind api-change
/triage accepted
The text was updated successfully, but these errors were encountered: