Skip to content

Update docs on new AKS certificate changes and relative agent configuration changes that are necessary #30171

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.

Sign up for GitHub

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

Draft
wants to merge 5 commits into
base: master
Choose a base branch
from
Draft

Update docs on new AKS certificate changes and relative agent configuration changes that are necessary #30171

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
0cae0a9
Include configuration change for AKS Kubelet certificate changes
mrdoggopat Jun 27, 2025
994a053
Add regions that are affected
mrdoggopat Jun 27, 2025
68b4ea2
Add details if disabling kubelet cert rotation
mrdoggopat Jun 27, 2025
38a80cd
Remove temporal word
mrdoggopat Jun 27, 2025
17b224f
Reformat the sentences.
mrdoggopat Jun 27, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions content/en/containers/kubernetes/distributions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -141,6 +141,16 @@

The AKS Kubelet certificate requires changing the Kubelet host to the `spec.nodeName` and the `hostCAPath` location of the certificate, as seen in the previous snippets. This enables TLS verification. Without these changes, the Agent cannot connect to the Kubelet.

However, AKS has changed how they structure their certificates relative to the [June 17th 2025 release][13], which is rolled out for East US and UK South. You can read more about this [in the Azure documentation here][14]. If your AKS cluster is located in one of the aforementioned regions and you are upgrading either:

Check notice on line 144 in content/en/containers/kubernetes/distributions.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.sentencelength 

Suggestion: Try to keep your sentence length to 25 words or fewer.
- Your AKS node pool from version 1.27 or later to a newer version.
- The node image from `202501.12.0` to a more recent version.

Make the following changes to the agent configuration:
- Change the `hostCAPath` to `/var/lib/kubelet/pki/kubelet-server-current.pem`.
- Optionally, you can remove the `spec.nodeName` configuration entirely since this new certificate path does not require changing the Kubelet host to `spec.nodeName` anymore.

If you choose to upgrade and disable [Kubelet serving certificate rotation][15] then you can keep the previous configurations.

### Without TLS verification

In some clusters, DNS resolution for `spec.nodeName` inside Pods does not work in AKS. This affects:
Expand Down Expand Up @@ -607,3 +617,6 @@
[10]: https://cloud.google.com/kubernetes-engine/docs/how-to/autopilot-spot-pods
[11]: https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-compute-classes
[12]: https://cloud.google.com/kubernetes-engine/docs/how-to/disable-kubelet-readonly-port
[13]: https://github.com/Azure/AKS/releases/tag/2025-06-17
[14]: https://learn.microsoft.com/en-us/azure/aks/certificate-rotation
[15]: https://learn.microsoft.com/en-us/azure/aks/certificate-rotation#disable-kubelet-serving-certificate-rotation
Loading