Add Kubernetes AgentInterface E2E backend

[nubtron]

What does this PR do?

Adds a KubernetesAgent implementation of ddev's existing AgentInterface for running integration E2E checks from inside a disposable Kubernetes cluster.

Today we have DockerAgent and VagrantAgent, this PR adds a third choice.

Usage:

@pytest.fixture(scope='session')
def dd_environment():
    with kind_run(conditions=[setup_integration]) as kubeconfig:
        instance = {'openmetrics_endpoint': METRICS_ENDPOINT}
        metadata = {
            'agent_type': 'kubernetes',
            'kubernetes': {
                'kubeconfig': kubeconfig,
            },
        }

        yield instance, metadata

Status Quo:

New Option:

Conversion example

#24642 converts Kuma to KubernetesAgent.

Motivation

Running the Agent outside the cluster requires port forwarding, introduces additional startup races, and doesn't allow us to test autodiscovery. Creating the Agent container in a pod inside the cluster solves these problems.

Limitations

he backend is not intended for shared or pre-existing clusters. Support for that could be added easily but I wanted to keep this PR small.

Validation

• integrations-core pre-commit linters
• focused Kubernetes Agent and environment lifecycle tests: 33 passed
• ddev Ruff formatting/checks and mypy
• coverage for manifest creation, RBAC, package/configuration synchronization, invocation, reload, shell, logs, no-op Agent teardown, and failed fixture-teardown state retention
• full Kind E2E validation for the converted Kuma, Argo CD, KEDA, Kyverno, Calico, Argo Rollouts, and Tekton integrations

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

[datadog-prod-us1-4]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 95.19%
• Overall Coverage: 88.51%

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

Review from HadhemiDD is dismissed. Related teams and files:

• agent-integrations
  • datadog_checks_dev/changelog.d/24639.added
  • datadog_checks_dev/datadog_checks/dev/plugin/pytest.py
  • ddev/changelog.d/24639.added
  • ddev/src/ddev/cli/env/init.py
  • ddev/src/ddev/cli/env/agent.py
  • ddev/src/ddev/cli/env/logs.py
  • ddev/src/ddev/cli/env/reload.py
  • ddev/src/ddev/cli/env/shell.py
  • ddev/src/ddev/cli/env/show.py
  • ddev/src/ddev/cli/env/start.py
  • ddev/src/ddev/cli/env/stop.py
  • ddev/src/ddev/e2e/agent/init.py
  • ddev/src/ddev/e2e/agent/docker.py
  • ddev/src/ddev/e2e/agent/image.py
  • ddev/src/ddev/e2e/agent/interface.py
  • ddev/src/ddev/e2e/agent/kubernetes.py
  • ddev/src/ddev/e2e/agent/vagrant.py
  • ddev/tests/cli/env/test_agent.py
  • ddev/tests/cli/env/test_logs.py
  • ddev/tests/cli/env/test_start.py
  • ddev/tests/cli/env/test_stop.py
  • ddev/tests/e2e/agent/test_kubernetes.py
  • docs/developer/ddev/plugins.md
  • docs/developer/ddev/test.md

[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

[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:   0 (always emitted)
Diff:            empty (no diff information)

Learn more about CI impact filtering