tekton: add container-based config discovery support

[vitkyrka]

What does this PR do?

Adds container-based config discovery support to tekton.

Known gap: the Triggers Controller's metrics endpoint (triggers_controller_endpoint, port 9000) is not covered by this PR. Its Deployment declares no containerPort on the pod spec at all — the port is only exposed via a separately-created Kubernetes Service object (confirmed both in the upstream tektoncd/triggers release manifests and on a live cluster via kubectl get pod -o yaml). The Agent's Kubelet-based Autodiscovery derives candidate ports from a pod's own declared container ports, so it never sees this port — the same class of limitation documented for Calico's own discovery attempt. Only the Pipelines Controller (port 9090, which does declare a containerPort named metrics) is covered here.

AD identifier: Tekton's official release images are built with ko and published under content-hash-suffixed names (e.g. ghcr.io/tektoncd/pipeline/controller-10a3e32792f33651396d02b6855a6e36) rather than a human-readable short name. This hash is stable across releases — confirmed identical between the tektoncd/pipeline v1.0.0 and v1.14.0 GitHub release manifests — and is the exact image every real deployment applying the standard release YAML runs, so it's used verbatim as the ad_identifiers value.

Base branch note: this branch is based on the not-yet-merged vwhitchurch/keda-discovery branch, which adds the shared Kubernetes-discovery E2E helpers (datadog_checks_dev/datadog_checks/dev/kube_discovery.py) this PR depends on. The diff against master therefore also includes keda's own discovery changes; rebase onto master once that branch merges.

Port selection rationale: Port 9090 is the Pipelines Controller's official documented default Prometheus metrics port.

Motivation

https://datadoghq.atlassian.net/browse/DSCVR-609

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

[datadog-prod-us1-5]

 

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 33.33%
• Overall Coverage: 71.01% (-17.39%)

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