Run KEDA E2E with the Kubernetes Agent backend

[nubtron]

What does this PR do?

Migrates the KEDA Kind E2E to the Kubernetes Agent backend introduced in #24639. The check now reaches KEDA through the in-cluster Service DNS endpoint, http://keda-operator-metrics-apiserver.keda.svc.cluster.local:8080/metrics, and returns the Kind kubeconfig in the Kubernetes backend metadata. This removes the external Docker Agent and persistent kubectl port-forward while preserving the existing setup, waits, instance shape, assertions, and timeouts.

Validation:

• cd ddev && hatch run -- ddev --no-interactive test -fs keda (passed)
• cd ddev && hatch run -- ddev --no-interactive test --lint keda (passed)
• cd ddev && hatch run -- ddev --no-interactive test keda (2 passed, 1 E2E skipped)
• cd ddev && hatch run -- ddev env start --dev keda py3.13-2.16.0 (passed)
• cd ddev && hatch run -- ddev env test --dev keda py3.13-2.16.0 (1 passed, 2 deselected)
• cd ddev && hatch run -- ddev env stop keda py3.13-2.16.0 (passed)

Motivation

Exercise KEDA from the same Kubernetes network as the Agent and validate the new backend from #24639 without maintaining a host-side port-forward process.

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-datadog-us1-prod]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 89.06% (+3.77%)

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

[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