Update docs on new AKS certificate changes and relative agent configuration changes that are necessary #30171
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
AKS may have changed how they structure their certificates again. Relative to the June 17th release: https://github.com/Azure/AKS/releases/tag/2025-06-17
/etc/kubernetes/certs/kubeletserver.crt
to/var/lib/kubelet/pki/kubelet-server-current.pem
once they upgrade their 1.27+ nodes to a higher versionThis may impact customers that don't use tlsVerify set to false but opt to give the agent the SSL cert following the docs: https://docs.datadoghq.com/containers/kubernetes/distributions/?tab=helm#AKS
This documentation update is to cover this in the event the customers run into issues with the agent when they upgrade their AKS nodes.