aks provider support#3150
Conversation
c1c5b92 to
711d01b
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c1c5b9282f
ℹ️ 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".
| - /manager | ||
| args: | ||
| - --enable-leader-election | ||
| - --enable-leader-election=false |
There was a problem hiding this comment.
Restore leader election in manager manifests
config/default and config/test-v1 both include ../manager, so this base Deployment is what users render/install. With this flag forced to false, any rolling update (the Deployment defaults allow a surge pod even with replicas: 1) or manual scale-out starts multiple active controller managers; the flag help in cmd/main.go says leader election is what ensures only one active manager. Please keep leader election enabled in the shipped manifest.
Useful? React with 👍 / 👎.
| } | ||
| } | ||
|
|
||
| provider := instance.GetAnnotations()[kubernetes.ProviderAnnotationKey] |
There was a problem hiding this comment.
Wire AKS support to the public Helm/CRD input
Here the AKS capability is driven solely by the datadoghq.com/provider annotation on the generated DDAI. The Helm compatibility path that users reported (providers.aks.enabled) still maps to "" in cmd/yaml-mapper/mapper/mapping_datadog_helm_to_datadogagent_crd.yaml, and no CRD field was added, so a DatadogAgent/Helm conversion using global.providers.aks.enabled: true still produces no DD_ADMISSION_CONTROLLER_ADD_AKS_SELECTORS. Please wire that public input to this provider value.
Useful? React with 👍 / 👎.
🛑 Gate Violations
ℹ️ Info🎯 Code Coverage (details) Useful? React with 👍 / 👎 This comment will be updated automatically if new data arrives.🔗 Commit SHA: 711d01b | Docs | Datadog PR Page | Give us feedback! |
gabedos
left a comment
There was a problem hiding this comment.
lgtm
nit: could we add a unit test that covers the expected changes for each provider? this would help us ensure that code changes don't introduce any regressions in the final manifest for the different providers (aks, gke, eks, etc)
What does this PR do?
CONTP-1567
Adds support for
aksprovider supported in helm.Easiest to review commit-by-commit:
228abde refactor provider capabilities to drop
NodeAgentfor naming.711d01b support
aksprovider to customize DCA config.Motivation
Related issue #2746.
Additional Notes
Anything else we should know when reviewing?
Minimum Agent Versions
Are there minimum versions of the Datadog Agent and/or Cluster Agent required?
Describe your test plan
user operator renderer or kind cluster to generate DCA Deployment manifest
verify DCA container has env var
spec.features.admissionController.enabled: false)DD_ADMISSION_CONTROLLER_ADD_AKS_SELECTORSshouldn't be addedChecklist
bug,enhancement,refactoring,documentation,tooling, and/ordependenciesqa/skip-qalabel