[CASCL-1493] change autoscaling profile values and descriptions#37647
[CASCL-1493] change autoscaling profile values and descriptions#37647alekseidiukov wants to merge 1 commit into
Conversation
|
/review |
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
There was a problem hiding this comment.
🤖 Automated review by Claude. AI-generated; verify before acting.
One consistency nit on the new Optimize Balance scale-down wording. The YAML and stabilization-window updates look internally consistent with the surrounding prose.
Reviewed f280090fb90049a5af8136102de6c0c915f8d4ee — workflow run
| - **Optimize cost**: high CPU utilization target, aggressive scale-down, lowest replica floor. Best for stateless, cost-sensitive workloads. | ||
| - **Optimize balance**: moderate utilization target, balanced scale-up and scale-down. Best for most stateless workloads. | ||
| - **Optimize performance**: conservative utilization target, slow scale-down, higher replica floor. Best for stateful or critical services. | ||
| - **Optimize balance**: moderate utilization target, fast scale-up, balanced scale-down. Best for most stateless workloads. |
There was a problem hiding this comment.
Suggestion: The Optimize Balance template is described as having a balanced scale-down here (and in the cluster-profile table at line 476), but the dedicated tab at line 305 calls the same setting a conservative scale-down and says the controller removes it slowly. Same profile, three different adjectives — pick one so readers comparing the wizard summary, profile table, and tab description don't wonder whether they describe the same behavior.
| - **Optimize balance**: moderate utilization target, fast scale-up, balanced scale-down. Best for most stateless workloads. | |
| - **Optimize balance**: moderate utilization target, fast scale-up, conservative scale-down. Best for most stateless workloads. |
1 participant
What does this PR do? What is the motivation?
Update DPA preset scale-up stabilization window values and profile descriptions to match the new defaults that we agreed upon in this document.
Merge readiness
For Datadog employees:
<name>/<description>convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Additional notes