Run Kuma E2E with the Kubernetes Agent backend

[nubtron]

What does this PR do?

Migrates Kuma's existing Kind E2E environment to the Kubernetes Agent backend.

The test fixture now:

• deploys Kuma to a Kind cluster with Helm and waits for the control-plane deployment to become ready;
• runs the Datadog Agent inside the Kind cluster;
• reaches Kuma through its in-cluster Service DNS endpoint (http://kuma-control-plane.kuma-system.svc.cluster.local:5680/metrics);
• removes the host-side kubectl port-forward processes and endpoint plumbing;
• fails environment setup immediately when Kubernetes or Helm commands fail.

The Kuma integration assertions are unchanged: the E2E still exercises the Helm-deployed Kuma control plane and verifies the expected Kuma metrics.

Motivation

Run the existing Kuma E2E through the Kubernetes Agent path and verify in-cluster service discovery without host-local endpoint plumbing. This PR changes only the E2E fixture; it does not change the Kuma check or production behavior.

Validation

• ddev --no-interactive test -fs kuma
• Kuma unit suite: 27 passed
• E2E test ran manually on laptop and workspace
• Kind E2E with the local base package: 2 passed
• Environment cleanup confirmed that the temporary Kind cluster is deleted

Review checklist

• 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, add the backport/<branch-name> label and a backport PR will be opened automatically after merge.

[datadog-datadog-prod-us1-2]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 33.33%
• Overall Coverage: 86.90% (-1.62%)

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

[cit-pr-commenter-54b7da]

evalya-impact-summary

evalya impact analysis

Impact analysis: RUN-ALL — every test task will run
Trigger:         empty diff (default branch, scheduled run, or shallow-clone fallback)
Test tasks:      0 (all selected)
Publish tasks:   1 (always emitted)
Diff:            empty (no diff information)

Learn more about CI impact filtering

[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