Skip to content

[TON-743] Add managed DatadogAgent settings to the EKS add-on chart - #3269

Open
fanny-jiang wants to merge 3 commits into
mainfrom
fanny/TON-723/operator-addon-marketplace-lifecycle
Open

[TON-743] Add managed DatadogAgent settings to the EKS add-on chart#3269
fanny-jiang wants to merge 3 commits into
mainfrom
fanny/TON-723/operator-addon-marketplace-lifecycle

Conversation

@fanny-jiang

@fanny-jiang fanny-jiang commented Jul 16, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds managed DatadogAgent lifecycle settings and Kubernetes resources to the Datadog Operator EKS add-on chart.

Motivation

After installing the Operator EKS add-on, the EKS instrumenter needs a chart contract for requesting DatadogAgent creation and removal.

Additional Notes

This chart change is independent of credentials sync and add-on installation. It should be released after the Operator runtime support is available.

Minimum Agent Versions

  • Agent: N/A
  • Cluster Agent: N/A

Describe your test plan

  • Parsed the Marketplace schema with jq.
  • Linted, rendered, and packaged the wrapper chart with the pinned Operator dependency.

Checklist

  • PR has at least one valid label: bug, enhancement, refactoring, documentation, tooling, and/or dependencies
  • PR has a milestone or the qa/skip-qa label
  • All commits are signed (see: signing commits)

@fanny-jiang fanny-jiang added the enhancement New feature or request label Jul 16, 2026
@datadog-prod-us1-3

This comment has been minimized.

@fanny-jiang fanny-jiang changed the title Add lifecycle settings to the EKS add-on chart Add managed Agent installation settings to the EKS add-on chart Jul 16, 2026
@fanny-jiang fanny-jiang changed the title Add managed Agent installation settings to the EKS add-on chart [TON-743] Add managed Agent installation settings to the EKS add-on chart Jul 21, 2026
@fanny-jiang fanny-jiang added this to the v1.30.0 milestone Jul 24, 2026
@fanny-jiang
fanny-jiang force-pushed the fanny/TON-723/operator-addon-marketplace-lifecycle branch from 3c792a1 to 0fc2f9c Compare August 5, 2026 20:51
@fanny-jiang fanny-jiang changed the title [TON-743] Add managed Agent installation settings to the EKS add-on chart [TON-743] Add managed DatadogAgent settings to the EKS add-on chart Aug 5, 2026
@fanny-jiang
fanny-jiang marked this pull request as ready for review August 5, 2026 20:54
@fanny-jiang
fanny-jiang requested a review from a team August 5, 2026 20:54

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 0fc2f9c755

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +127 to +129
"apiKeyExistingSecret": {
"type": "string"
},

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove the duplicate secret schema key

This adds a second datadog-operator.apiKeyExistingSecret entry in the same JSON object, so parsers that accept duplicate keys keep this later string-only schema and discard the existing nullable/minLength definition above. In configurations that explicitly leave the chart default as null, validation now rejects a value that was previously allowed; keep the original definition or merge any intended changes into it.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant