Pass DatadogAgent spec through managed EKS installation intents - #3497
Draft
fanny-jiang wants to merge 1 commit into
Draft
fanny-jiang wants to merge 1 commit into
fanny-jiang wants to merge 1 commit into
Conversation
|
🎯 Code Coverage (details) 🔗 Commit SHA: f2cdb22 | Docs | View more details | Give us feedback! |
This branch has not been deployed
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
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?
Adds a v2 managed EKS Agent installation intent that can carry a partial or complete
DatadogAgentSpec.The Operator strictly decodes the supplied spec using the DDA API version bundled with the add-on, preserves managed cluster identity, credentials, and Linux scheduling settings, and rejects equivalent managed environment variable overrides. Existing v1 intents remain supported.
The EKS add-on configuration schema exposes a stable
datadogAgent.specenvelope without duplicating the complete DDA CRD schema.Motivation
Managed EKS installation needs a feature-agnostic way for the onboarding service to supply product-owned DDA defaults. This avoids adding a new intent field and Marketplace schema change for each DDA feature.
Tracking: https://datadoghq.atlassian.net/browse/TON-931
Additional Notes
The onboarding service must emit v2 only after selecting an add-on version containing this support. Existing v1 installations are not migrated automatically.
Corresponding
dd-sourcechange: https://github.com/ddoghq/dd-source/pull/99364Minimum Agent Versions
No additional minimum Datadog Agent or Cluster Agent version.
Describe your test plan
go test ./pkg/fleet/go vet ./pkg/fleet/git diff --checkChecklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel