Add built-in vertical-only DPA profile

[TitouanGuesdon]

Add a new "datadog-vertical-only" built-in cluster profile that creates DPAs with only vertical scaling enabled (resource rightsizing) and horizontal scaling disabled. This is useful for workloads where replica count should remain fixed but container resources should be auto-tuned.

What does this PR do?

Motivation

Describe how you validated your changes

Additional Notes

[github-actions]

AI review by Codex (OpenAI) - workflow run

The patch is correct. The new profile disables both horizontal scaling directions and fallback while enabling automatic vertical updates for all containers. No actionable issues were found. Tests could not run in the read-only environment because the Go module cache is unavailable.

[datadog-prod-us1-3]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 62.78% (+4.18%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 1552456 | Docs | Give us feedback!}

[dd-octo-sts]

Files inventory check summary

File checks results against ancestor 8d6360c8:

Results for datadog-agent_7.86.0~devel.git.315.1552456.pipeline.143717458-1_amd64.deb:

No change detected

Results for datadog-iot-agent_7.86.0~devel.git.315.1552456.pipeline.143717458-1_amd64.deb:

No change detected

[dd-octo-sts]

Static quality checks

✅ Please find below the results from static quality gates
Comparison made with ancestor 8d6360c
📊 Static Quality Gates Dashboard
🔗 SQG Job

Successful checks

Info

	Quality gate	Change	Size (prev → curr → max)
✅	agent_deb_amd64	+4.66 KiB (0.00% increase, -0.09% of buffer)	755.202 → 755.207 → 760.520
✅	agent_rpm_amd64	+4.66 KiB (0.00% increase, -0.09% of buffer)	755.186 → 755.190 → 760.500
✅	agent_suse_amd64	+4.66 KiB (0.00% increase, -0.09% of buffer)	755.186 → 755.190 → 760.500
✅	docker_agent_amd64	+4.66 KiB (0.00% increase, -0.08% of buffer)	811.365 → 811.369 → 816.720
✅	docker_agent_jmx_amd64	+4.66 KiB (0.00% increase, -0.08% of buffer)	1002.235 → 1002.239 → 1007.590
✅	docker_cluster_agent_arm64	+64.75 KiB (0.03% increase, -1.95% of buffer)	224.162 → 224.225 → 227.410

26 successful checks with minimal change (< 2 KiB)

	Quality gate	Current Size
✅	agent_deb_amd64_fips	688.224 MiB
✅	agent_heroku_amd64	319.086 MiB
✅	agent_rpm_amd64_fips	688.208 MiB
✅	agent_rpm_arm64	725.738 MiB
✅	agent_rpm_arm64_fips	664.321 MiB
✅	agent_suse_amd64_fips	688.208 MiB
✅	agent_suse_arm64	725.738 MiB
✅	agent_suse_arm64_fips	664.321 MiB
✅	docker_agent_arm64	806.544 MiB
✅	docker_agent_jmx_arm64	986.194 MiB
✅	docker_cws_instrumentation_amd64	7.443 MiB
✅	docker_cws_instrumentation_arm64	6.877 MiB
✅	docker_dogstatsd_amd64	39.547 MiB
✅	docker_dogstatsd_arm64	37.629 MiB
✅	docker_host_profiler_amd64	308.722 MiB
✅	docker_host_profiler_arm64	319.865 MiB
✅	dogstatsd_deb_amd64	30.289 MiB
✅	dogstatsd_deb_arm64	28.278 MiB
✅	dogstatsd_rpm_amd64	30.289 MiB
✅	dogstatsd_suse_amd64	30.289 MiB
✅	iot_agent_deb_amd64	47.371 MiB
✅	iot_agent_deb_arm64	43.837 MiB
✅	iot_agent_deb_armhf	44.652 MiB
✅	iot_agent_rpm_amd64	47.371 MiB
✅	iot_agent_suse_amd64	47.370 MiB
✅	docker_cluster_agent_amd64	211.197 MiB

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Job ID: ee2fbffb-5737-4818-8c6a-69082a58e527

Baseline: 8d6360c
Comparison: 1552456
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_metrics_logs	memory utilization	+2.00	[+1.77, +2.23]	1	Logs bounds checks dashboard
➖	quality_gate_security_mean_fs_load	memory utilization	+0.64	[+0.60, +0.68]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_cpu	% cpu utilization	+0.57	[+0.35, +0.80]	1	Logs
➖	dsd_uds_client_drop_detector_cpu	% cpu utilization	+0.52	[+0.02, +1.01]	1	Logs
➖	python_openmetrics	% cpu utilization	+0.21	[-0.47, +0.90]	1	Logs bounds checks dashboard
➖	quality_gate_security_idle	memory utilization	+0.17	[+0.13, +0.21]	1	Logs bounds checks dashboard
➖	quality_gate_security_no_fs_load	memory utilization	-0.13	[-0.20, -0.05]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.15	[-0.19, -0.12]	1	Logs bounds checks dashboard
➖	quality_gate_idle_all_features	memory utilization	-0.33	[-0.41, -0.26]	1	Logs bounds checks dashboard
➖	quality_gate_private_action_runner	memory utilization	-0.37	[-0.50, -0.25]	1	Logs bounds checks dashboard
➖	quality_gate_logs	% cpu utilization	-0.47	[-1.32, +0.39]	1	Logs bounds checks dashboard
➖	dsd_uds_10mb_3k_timestamped_contexts_memory	memory utilization	-0.52	[-0.74, -0.30]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	observed_value	links
✅	python_openmetrics	checks_execution_time	10/10	76.83 ≤ 100	bounds checks dashboard
✅	python_openmetrics	cpu_usage	10/10	1339.11 ≤ 1500	bounds checks dashboard
✅	python_openmetrics	memory_usage	10/10	4.32GiB ≤ 4.75GiB	bounds checks dashboard
✅	quality_gate_idle	intake_connections	10/10	4 ≤ 5	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	176.86MiB ≤ 181MiB	bounds checks dashboard
✅	quality_gate_idle	total_bytes_received	10/10	764.52KiB ≤ 819.20KiB	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	2 ≤ 5	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	475.02MiB ≤ 542MiB	bounds checks dashboard
✅	quality_gate_idle_all_features	total_bytes_received	10/10	1.13MiB ≤ 1.25MiB	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	16 ≤ 40	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	212.37MiB ≤ 228MiB	bounds checks dashboard
✅	quality_gate_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_logs	total_bytes_received	10/10	263.91MiB ≤ 292MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	365.69 ≤ 2000	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	19 ≤ 40	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	411.88MiB ≤ 455MiB	bounds checks dashboard
✅	quality_gate_metrics_logs	missed_bytes	10/10	0B = 0B	bounds checks dashboard
✅	quality_gate_metrics_logs	total_bytes_received	10/10	0.95GiB ≤ 1.04GiB	bounds checks dashboard
✅	quality_gate_private_action_runner	memory_usage	10/10	74.02MiB ≤ 77MiB	bounds checks dashboard
✅	quality_gate_security_idle	cpu_usage	10/10	29.51 ≤ 100	bounds checks dashboard
✅	quality_gate_security_idle	memory_usage	10/10	330.35MiB ≤ 357MiB	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	cpu_usage	10/10	63.92 ≤ 200	bounds checks dashboard
✅	quality_gate_security_mean_fs_load	memory_usage	10/10	309.72MiB ≤ 337MiB	bounds checks dashboard
✅	quality_gate_security_no_fs_load	cpu_usage	10/10	23.35 ≤ 100	bounds checks dashboard
✅	quality_gate_security_no_fs_load	memory_usage	10/10	313.54MiB ≤ 348MiB	bounds checks dashboard

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

CI Pass/Fail Decision

✅ Passed. All Quality Gates passed.

• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_private_action_runner, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_mean_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_idle, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
• quality_gate_security_no_fs_load, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check total_bytes_received: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.