-
Notifications
You must be signed in to change notification settings - Fork 43
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
Mega Issue: Supported AKS Kubelet Configuration #196
Comments
Is the kubelet configuration via karpenter node pool even working?
then inspected the kubelet settings on the node and found that the settings are not applied at all? I am not sure if
|
Azure Karpenter does reference the data structure internally for passing around kubelet configuration, but we do not allow customers to set the values yet. |
Tell us about your request
Karpenter Core plans on moving the kubelet configuration outside of the core api and instead have cloudproviders maintain their own set of supported kubelet configuration in the v1 api. The AKS provider needs a migration plan so that we can stay on track with keeping our core version synced close with upstream.
Also AKS supports the following kubelet configuration: https://learn.microsoft.com/en-us/azure/aks/custom-node-configuration?tabs=linux-node-pools#kubelet-configuration
We need to start implementing the propagation for all of the aks supported kubelet configuration so karpenter has feature parity. Perhaps we can also drive further discussion in other kubelet configuration features customers want and let them configure them through karpenter before rolling out to the wider audience at AKS.
This issue has been created to track
Attachments
See: kubernetes-sigs/karpenter#758 (comment)
Thread on Slack we talked about moving from cloud neutral configuration: https://kubernetes.slack.com/archives/C04JW2J5J5P/p1709226455964629
Community Note
The text was updated successfully, but these errors were encountered: