[CECO-2145] Use datadog.kubelet.useApiServer for GKE Autopilot
#29199
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tbavelier
changed the title
datadog.kubelet.useapiserver for GKE Autopilotdatadog.kubelet.useApiServer for GKE Autopilot
Preview links (active after the
|
urseberry
reviewed
May 7, 2025
| Datadog recommends that you specify resource limits for the Agent container. Autopilot sets a relatively low default limit (50m CPU, 100Mi memory) that may lead the Agent container to quickly OOMKill depending on your environment. If applicable, also specify resource limits for the Trace Agent and Process Agent containers. Additionally, you may wish to create a priority class for the Agent to ensure it is scheduled. | ||
| Datadog recommends that you specify resource limits for the Agent container. Autopilot sets a relatively low default limit (50m CPU, 100Mi memory) that may lead the Agent container to quickly OOMKill depending on your environment. If applicable, also specify resource limits for the Trace Agent, Process Agent and System-Probe containers. Additionally, you may wish to create a priority class for the Agent to ensure it is scheduled. | ||
|
|
||
| Starting with Agent `7.65.0+` and version `3.113.0+` of the Helm chart, we also recommend using `datadog.kubelet.useApiServer` for the Agent to query the pod list from the API server instead of the [deprecated read-only kubelet port][12]. |
There was a problem hiding this comment.
Suggested change
| Starting with Agent `7.65.0+` and version `3.113.0+` of the Helm chart, we also recommend using `datadog.kubelet.useApiServer` for the Agent to query the pod list from the API server instead of the [deprecated read-only kubelet port][12]. | |
| Starting with Agent `7.65.0+` and version `3.113.0+` of the Helm chart, Datadog recommends using `datadog.kubelet.useApiServer` for the Agent to query the pod list from the API server. Avoid using the [deprecated read-only kubelet port][12]. |
| @@ -237,6 +239,12 @@ datadog: | |||
| # Documentation: https://docs.datadoghq.com/getting_started/site/ | |||
| site: <DATADOG_SITE> | |||
|
|
|||
| # This option uses the API server to retrieve the node-level pod list from the API server. | |||
| # This is necessary to migrate away from the deprecated read-only kubelet port. | |||
There was a problem hiding this comment.
Suggested change
| # This is necessary to migrate away from the deprecated read-only kubelet port. | |
| # This setting is necessary to migrate away from the deprecated read-only kubelet port. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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? What is the motivation?
Merge instructions
Merge readiness: