Support kubelet.cpuManagerPolicy in NodePools

[olibenni]

Tell us about your request

I would like to provision some nodes with static CPU, without having a specific node template for those nodes.

Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?

Shipping a static CPU node with my provisioner.

Are you currently working around this issue?

I have a specific node template using userData to set the cpu manager policy to static.
As supported by aws/karpenter-provider-aws#2271

Additional Context

I'd rather not maintain multiple node templates if the only difference between them is the userData.

Attachments

No response

Community Note

• 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

[jonathan-innis]

@olibenni Are you blocked on this not being in the spec.kubelet today?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[Bryce-Soghigian]

/remove-lifecycle stale

[Bryce-Soghigian]

Would be good to start discussion if we can support all the values here: https://learn.microsoft.com/en-us/azure/aks/custom-node-configuration?tabs=linux-node-pools#linux-kubelet-custom-configuration one of which is cpuManagerPolicy.

[olibenni]

@jonathan-innis sorry for a super later reply.
This is not blocking me at all today. But I still believe, as @Bryce-Soghigian points out, that supporting all the kubectl values is helpful.

[jonathan-innis]

But I still believe, as @Bryce-Soghigian points out, that supporting all the kubectl values is helpful

It's a good point. We combined the conversation for AWS here: aws/karpenter-provider-aws#5833. We've gotten a number of requests to add non-scheduling related fields to the Kubelet Configuration and I figure that it will be good to combine all of this conversation into one place. It's on the AWS-side because there's pretty strong sentiment that we should move the kubelet block over to the NodeClass API as part of v1

[Bryce-Soghigian]

Started a thread here on the AKS side: Azure/karpenter-provider-azure#196