Graceful node shutdown configuration

[fiunchinho]

What would you like to be added (User Story)?

As a developer I'd like to be able to configure the graceful node shutdown options that are available in the kubelet, so that worker nodes are drained before being terminated.

Detailed Description

These options are not available as kubelet args, so they can't be configured using the kubeletExtraArgs field. They can only be configured from the config file.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

[fabriziopandini]

/triage accepted
This is a revival of #4464 (and also related to #3700), and it brings up again the question of what we should do with component config considered that this work is stalled in Kubernetes and there is no clear way forward

[killianmuldoon]

AFAIU users can provide a file through cloud-init to configure the kubelet via kubeletconfiguration. kubeadm also has the option to patch kubeletconfiguration. There's definitely routes to enabling this today in a CAPI/KCP/CAPBK cluster, but the user interface isn't exactly the nicest.

[fabriziopandini]

We should probably start documenting available options as a stop gap

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[fabriziopandini]

/priority important-longterm

[fabriziopandini]

The Cluster API project currently lacks enough active contributors to adequately respond to all issues and PRs.

We documented in https://cluster-api.sigs.k8s.io/tasks/bootstrap/kubeadm-bootstrap/kubelet-config available options to configure kubelet.

/close

[k8s-ci-robot]

@fabriziopandini: Closing this issue.

In response to this:

The Cluster API project currently lacks enough active contributors to adequately respond to all issues and PRs.

We documented in https://cluster-api.sigs.k8s.io/tasks/bootstrap/kubeadm-bootstrap/kubelet-config available options to configure kubelet.

/close

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.