Tag pod with affinities

[jbartosik]

What does this PR do?

Report info on pods node affinities

Motivation

Describe how you validated your changes

Details on the attached issue.

Possible Drawbacks / Trade-offs

Additional Notes

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 24c6f336-b5dd-4087-9e81-520a01b7b562

Baseline: c83838f
Comparison: 1110fd9
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	quality_gate_logs	% cpu utilization	+2.79	[-0.48, +6.07]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.99	[+0.20, +1.78]	1	Logs
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.74	[+0.06, +1.43]	1	Logs
➖	file_tree	memory utilization	+0.73	[+0.60, +0.86]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.22	[+0.13, +0.30]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	+0.18	[+0.14, +0.21]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency	egress throughput	+0.05	[-0.84, +0.94]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	+0.03	[-0.60, +0.67]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	+0.00	[-0.10, +0.11]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.00	[-0.75, +0.76]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	file_to_blackhole_0ms_latency_http1	egress throughput	-0.01	[-0.85, +0.83]	1	Logs
➖	file_to_blackhole_1000ms_latency_linear_load	egress throughput	-0.05	[-0.51, +0.41]	1	Logs
➖	file_to_blackhole_0ms_latency_http2	egress throughput	-0.06	[-0.84, +0.72]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.24	[-1.01, +0.54]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.93	[-1.00, -0.87]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http1	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http1	memory_usage	10/10
✅	file_to_blackhole_0ms_latency_http2	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency_http2	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency_linear_load	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	lost_bytes	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10
✅	quality_gate_logs	memory_usage	10/10

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_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.

[agent-platform-auto-pr]

Uncompressed package size comparison

Comparison with ancestor c83838f0eb1cfbea4afb3d4426e985e51d3661e8

Diff per package

package	diff	status	size	ancestor	threshold
datadog-agent-amd64-deb	0.15MB	⚠️	1191.19MB	1191.04MB	140.00MB
datadog-agent-x86_64-rpm	0.15MB	⚠️	1200.51MB	1200.36MB	140.00MB
datadog-agent-x86_64-suse	0.15MB	⚠️	1200.51MB	1200.36MB	140.00MB
datadog-agent-aarch64-rpm	0.10MB	⚠️	944.76MB	944.66MB	140.00MB
datadog-agent-arm64-deb	0.10MB	⚠️	935.46MB	935.36MB	140.00MB
datadog-heroku-agent-amd64-deb	0.07MB	⚠️	505.32MB	505.25MB	70.00MB
datadog-iot-agent-amd64-deb	0.05MB	⚠️	113.38MB	113.33MB	10.00MB
datadog-iot-agent-arm64-deb	0.05MB	⚠️	108.86MB	108.80MB	10.00MB
datadog-iot-agent-x86_64-rpm	0.05MB	⚠️	113.45MB	113.40MB	10.00MB
datadog-iot-agent-x86_64-suse	0.05MB	⚠️	113.45MB	113.40MB	10.00MB
datadog-iot-agent-aarch64-rpm	0.05MB	⚠️	108.93MB	108.87MB	10.00MB
datadog-dogstatsd-x86_64-rpm	0.00MB	✅	78.61MB	78.61MB	10.00MB
datadog-dogstatsd-x86_64-suse	0.00MB	✅	78.61MB	78.61MB	10.00MB
datadog-dogstatsd-amd64-deb	0.00MB	✅	78.53MB	78.53MB	10.00MB
datadog-dogstatsd-arm64-deb	0.00MB	✅	55.75MB	55.75MB	10.00MB

Decision

⚠️ Warning

[agent-platform-auto-pr]

Test changes on VM

Use this command from test-infra-definitions to manually test this PR changes on a VM:

inv aws.create-vm --pipeline-id=51906123 --os-family=ubuntu

Note: This applies to commit 1110fd9