Exercise Kubernetes Agent backend across Kind E2Es

[nubtron]

What does this PR do?

This draft is the aggregate validation PR for the Kubernetes Agent E2E project. It combines the frozen reusable backend and these seven exact Kind consumer source heads:

• Add Kubernetes AgentInterface E2E backend #24639 — Kubernetes AgentInterface backend: 2a6404339f79649eb3c01bdc795e2f2589ed7d55
• Run Kuma E2E with the Kubernetes Agent backend #24642 — Kuma: d945435538cc86f6e5167ff984e43b48f1f5fcc0
• Run Argo CD E2E with the Kubernetes Agent backend #24670 — Argo CD: 5f6000f85a5a60d940599b4f8ad42543e4891861
• Run KEDA E2E with the Kubernetes Agent backend #24671 — KEDA: cc0cdc6aceaa6131d9f2ef3512be622b9c832248
• Run Kyverno E2E with the Kubernetes Agent backend #24672 — Kyverno: c922643a9cd10eec1e9a1a25fb204a916ffd8bad
• Run Calico E2E with the Kubernetes Agent backend #24673 — Calico: 34d6c3b014bfdc44bf2c4d3f70604af81c0e8939
• Run Argo Rollouts E2E with the Kubernetes Agent backend #24674 — Argo Rollouts: 3c98d2761fbdca70922c4bd69eac904f5e552bec
• Run Tekton E2E with the Kubernetes Agent backend #24678 — Tekton: d863f4442467ff2875046b64e0132569926db91b

The refreshed aggregate head is 16919ea44518557c239e87aa5aa279438149d32a. The branch preserves the published aggregate history and adds signed merge commits for the backend and each source branch.

It explicitly excludes #24645 (Velero sentinel 73015423ce2f77a2c7650d467fd1333472a381a0) and #24647 (Helm sentinel 9504b5e727e2b15f030adaea99c71158d2a8733e), including their Velero, named-port, and Helm paths.

The integration fixtures run the real Agent inside their Kind clusters and use in-cluster Service DNS instead of persistent Agent-facing kubectl port-forward processes. This aggregate does not replace the independently reviewable source PRs; it provides one combined ref for aggregate CI and Agent-image validation.

Motivation

Validate the frozen #24639 backend and a representative set of single-node Kind consumers together in both ordinary PR CI and release-style targeted tests.

Branch-level lint and unit validation passed for the backend and seven consumer source branches before aggregation. Aggregate ddev lint (Ruff and mypy) and 35 focused backend/CLI tests also passed on refreshed head 16919ea44518557c239e87aa5aa279438149d32a. Aggregate CI and release-style tests are pending. No workflows were manually dispatched as part of this refresh.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add qa/required if this PR needs QA validation, or qa/skip-qa if it does not. Exactly one of the two is required.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[dd-octo-sts]

Validation Report

All 21 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and code coverage settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
qa-label	Validate the pull request declares whether it needs QA for the next Agent release	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run