[TON-743] Add managed DatadogAgent settings to the EKS add-on chart - #3269
[TON-743] Add managed DatadogAgent settings to the EKS add-on chart#3269fanny-jiang wants to merge 3 commits into
Conversation
This comment has been minimized.
This comment has been minimized.
3c792a1 to
0fc2f9c
Compare
There was a problem hiding this comment.
💡 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".
| "apiKeyExistingSecret": { | ||
| "type": "string" | ||
| }, |
There was a problem hiding this comment.
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 👍 / 👎.
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
Describe your test plan
jq.Checklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel