Document configuring Autodiscovery with the DatadogInstrumentation CRD#37532
Draft
Mathew-Estafanous wants to merge 1 commit into
Draft
Document configuring Autodiscovery with the DatadogInstrumentation CRD#37532Mathew-Estafanous wants to merge 1 commit into
Mathew-Estafanous wants to merge 1 commit into
Conversation
Add a new guide describing how to configure Autodiscovery checks for Kubernetes workloads through the DatadogInstrumentation custom resource (beta) instead of pod annotations, and cross-reference it from the existing Autodiscovery pages. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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?
Documents the new (beta) capability to configure Autodiscovery checks for Kubernetes workloads through the
DatadogInstrumentationcustom resource, instead of pod annotations. This lets users enable, update, and roll back integration configuration without editing pod specs or triggering Agent/application rollouts.Changes:
Configure Autodiscovery with the DatadogInstrumentation CRD(content/en/containers/guide/configure-autodiscovery-with-the-datadoginstrumentation-crd.md). Covers requirements, enabling the controller with the Datadog Operator (opt-in annotation) or Helm (datadog.instrumentationCrd.enabled), thetargetRef+spec.config.checksschema with a Redis example, endpoint/cluster checks viaServicetargets, precedence (annotations > CRD > static), one-resource-per-workload validation, status conditions, and limitations.containers/kubernetes/integrations.md: new "DatadogInstrumentation CRD" config-method tab + updated method list.containers/guide/autodiscovery-examples.md: intro note + further reading.getting_started/containers/autodiscovery.md: note in "Integration templates" + further reading.Requirements documented: Agent & Cluster Agent v7.81+, Datadog Operator v1.28+, or Helm chart v2.223.0+.
Merge instructions
Merge readiness:
Additional notes
The feature is in beta. The guide and cross-references are labeled accordingly.