Description

What problem are you trying to solve?

As a karpenter user running on openshift, i would like new nodes to have the label node-role.kubernetes.io/worker so that my cluster automation will behave as i expect. Karpenter does not allow some labels, notably those with the kubernetes.io prefix which are not well-known, to be filtered for or to be applied to new nodes. If karpenter could filter for, and add, any label then this would solve my problem.

How important is this feature to you?

This is fairly important for openshift as the label is used frequently. It is possible to work around this, but for long term usage on openshift a permanent solution would be better.

Openshift is not singular in this respect either, other cluster infrastructures have similar requirements. If karpenter is adding labels after a node has been created (ie not as a flag to kubelet) then it should be allowed to add any label that the user requests.

This issue was discussed at the Feb. 26 2024 community meeting.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment