Bump k8s.io/kubectl from 0.34.1 to 0.35.1

[dependabot]

Bumps k8s.io/kubectl from 0.34.1 to 0.35.1.

Commits

• 232a843 Update dependencies to v0.35.1 tag
• 093dc66 Merge pull request #136280 from seekskyworld/automated-cherry-pick-of-#135918...
• 6b218dd kubectl: Fix panic in exec terminal size queue
• 817cfc8 Merge remote-tracking branch 'origin/master' into release-1.35
• aeaf9d6 Bump golang.org/x/crypto to v0.45.0
• a319be8 Merge pull request #135131 from Dev1622/sig-storage/mock-expand-flake-fix
• e39563a vendor: update vendor and license metadata after replacing BeTrue usage in cs...
• 579bcf1 Resolve lint restriction on BeTrue by introducing Succeed() with contextual e...
• d13f830 Update vendored dependencies
• 9f47edd Merge pull request #134870 from pmengelbert/pmengelbert/kuberc/4
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cit-pr-commenter-54b7da]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: ffaaccbf-8b5c-4717-a87f-69048eab7079

Baseline: d1bd885
Comparison: 4a81e73
Diff

Optimization Goals: ✅ No significant changes detected

Experiments ignored for regressions

Regressions in experiments with settings containing erratic: true are ignored.

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.35	[+0.22, +6.48]	1	Logs

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	docker_containers_cpu	% cpu utilization	+3.35	[+0.22, +6.48]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	+2.32	[+2.22, +2.43]	1	Logs
➖	quality_gate_logs	% cpu utilization	+1.16	[-0.36, +2.69]	1	Logs bounds checks dashboard
➖	ddot_metrics_sum_cumulativetodelta_exporter	memory utilization	+0.42	[+0.19, +0.65]	1	Logs
➖	docker_containers_memory	memory utilization	+0.24	[+0.17, +0.31]	1	Logs
➖	ddot_metrics	memory utilization	+0.20	[-0.01, +0.41]	1	Logs
➖	otlp_ingest_metrics	memory utilization	+0.17	[+0.02, +0.33]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	+0.06	[-0.32, +0.43]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	+0.01	[-0.04, +0.05]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	+0.00	[-0.42, +0.43]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.10, +0.11]	1	Logs
➖	uds_dogstatsd_to_api_v3	ingress throughput	-0.00	[-0.14, +0.13]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.00	[-0.13, +0.12]	1	Logs
➖	file_to_blackhole_0ms_latency	egress throughput	-0.03	[-0.51, +0.45]	1	Logs
➖	ddot_metrics_sum_cumulative	memory utilization	-0.03	[-0.19, +0.13]	1	Logs
➖	ddot_metrics_sum_delta	memory utilization	-0.08	[-0.27, +0.11]	1	Logs
➖	uds_dogstatsd_20mb_12k_contexts_20_senders	memory utilization	-0.08	[-0.13, -0.03]	1	Logs
➖	quality_gate_metrics_logs	memory utilization	-0.18	[-0.39, +0.02]	1	Logs bounds checks dashboard
➖	otlp_ingest_logs	memory utilization	-0.22	[-0.32, -0.13]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	-0.30	[-0.34, -0.26]	1	Logs bounds checks dashboard
➖	quality_gate_idle	memory utilization	-0.35	[-0.40, -0.31]	1	Logs bounds checks dashboard
➖	file_tree	memory utilization	-0.42	[-0.47, -0.36]	1	Logs
➖	ddot_logs	memory utilization	-0.50	[-0.56, -0.44]	1	Logs

Bounds Checks: ✅ Passed

perf	experiment	bounds_check_name	replicates_passed	links
✅	docker_containers_cpu	simple_check_run	10/10
✅	docker_containers_memory	memory_usage	10/10
✅	docker_containers_memory	simple_check_run	10/10
✅	file_to_blackhole_0ms_latency	lost_bytes	10/10
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	lost_bytes	10/10
✅	file_to_blackhole_1000ms_latency	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_500ms_latency	lost_bytes	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10
✅	quality_gate_idle	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_idle_all_features	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_logs	memory_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	cpu_usage	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	intake_connections	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	lost_bytes	10/10	bounds checks dashboard
✅	quality_gate_metrics_logs	memory_usage	10/10	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 intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
• quality_gate_logs, bounds check intake_connections: 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_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 memory_usage: 10/10 replicas passed. Gate passed.
• quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.