The added startupProbe in the Helm Chart 3.67.0 appears to conflict with the expected pattern for the Agent in GKE AutoPilot, causing it to get blocked by the GKE Warden. This just adds a simple "if NOT gke.autopilot -> add startup probe".
Does not make the changes to the Cluster Agent or Cluster Check Runner, as those were not impacted.
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)
fixes #1436
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
[ ] Chart Version bumped
[ ] Documentation has been updated with helm-docs (run: .github/helm-docs.sh)
[ ] CHANGELOG.md has been updated
[ ] Variables are documented in the README.md
[ ] For Datadog Operator chart or value changes update the test baselines (run: make update-test-baselines)
What this PR does / why we need it:
The added
startupProbein the Helm Chart 3.67.0 appears to conflict with the expected pattern for the Agent in GKE AutoPilot, causing it to get blocked by the GKE Warden. This just adds a simple "if NOT gke.autopilot -> add startup probe".Does not make the changes to the Cluster Agent or Cluster Check Runner, as those were not impacted.
Which issue this PR fixes
(optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged)Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]
.github/helm-docs.sh)CHANGELOG.mdhas been updatedREADME.mdmake update-test-baselines)