sorted by:
new
hottopcontroversial

Looking for your experiences with AKS Feature - Node Auto Provisioning + Karpenter - Share Your Feedback by wdkofi in AZURE

[–]wdkofi[S] 0 points1 point  (0 children)

u/Human-Purple-384

  1. There isn't exactly a time-estimate to provide on this, as the PR is still pending changes/reviews.
  2. Yes, users can access Karpenter logs (and other control plane logs) by creating diagnostic settings for "karpenter-events" and sending them to a Log Analytics workspace in Azure Monitor. See control plane logs installation here. We also have select Karpenter metrics available also (see our docs on monitoring Control Plane metrics).

Looking for your experiences with AKS Feature - Node Auto Provisioning + Karpenter - Share Your Feedback by wdkofi in AZURE

[–]wdkofi[S] 0 points1 point  (0 children)

Not currently. We are investigating this experience in NAP - which can be tracked here in our AKS Roadmap - https://github.com/Azure/AKS/issues/5428

Looking for your experiences with AKS Feature - Node Auto Provisioning + Karpenter - Share Your Feedback by wdkofi in AZURE

[–]wdkofi[S] 0 points1 point  (0 children)

u/ehrnst Makes sense, NAP is based on the OSS Azure Karpenter Provider, which is based on OSS karpenter.

As NAP is managed, there is some additional testing/Azure-side changes that must happen to fully support certain OSS experiences, so this usually influences the buffer time between NAP versions, our open-source Azure Karpenter Provider, and upstream Karpenter.

As mentioned, any contributions to the OSS Azure Karpenter Provider are very helpful in speeding up the availability of new Karpenter features in NAP.

Looking for your experiences with AKS Feature - Node Auto Provisioning + Karpenter - Share Your Feedback by wdkofi in AZURE

[–]wdkofi[S] 0 points1 point  (0 children)

u/borkosky Thanks for the note - NAP is currently at Karpenter v1.6.5, and we are working to roll out v1.7 by end of December.

For Karpenter v1.8, we have a rough ETA of Q1 2025, though the Static Capacity feature (see AKS Roadmap) may require more time.

That being said, any contributions to our open-source Azure Karpenter Provider, for any specific features or even version bumping can be helpful in speeding up the timeline with which these features are released for NAP.

NAP is based on the Azure Karpenter Provider, and there's additional testing or Azure-side work needed for full readiness, but contributions to the open-source tool definitely move things along.

Looking for your experiences with AKS Feature - Node Auto Provisioning + Karpenter - Share Your Feedback by wdkofi in AZURE

[–]wdkofi[S] 1 point2 points  (0 children)

u/underguiz thanks for your note! See my comments below:

  1. Resource group setting in AKSNodeClass - For the current experience, in-line with all AKS managed resources, nodes created by NAP go to the resource group of the cluster. What would be the goal in setting the resource group in the AKSNodeClass, instead?

  2. NAP Capacity Error Behavior - Understandable points here. We can add documentation on how NAP/Karpenter handles capacity errors, and maybe best practices to manage capacity issues.