Fix auto-discovery for latest versions on Kubernetes #9577
Merged
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.
What does this PR do?
Leverages the
possible_prometheus_urls
parameter introduced by #9573 in the auto-discovery configuration file.Motivation
Make the agent able to automatically monitor the Kube API server on most recent versions of Kubernetes without requiring too much user setup.
The goad is to simplify the Kubernetes control plane monitoring setup described in DataDog/documentation#10828.
Additional Notes
Depending on the Kubernetes distribution, the API server can listen on two different default ports:
8443
and6443
.We need to try both in the auto-discovery configuration.
Review checklist (to be filled by reviewers)
changelog/
andintegration/
labels attached