tekton: add container-based config discovery support - #24526
Draft
vitkyrka wants to merge 1 commit into
Draft
Conversation
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: df9961d | Docs | Datadog PR Page | Give us feedback! |
vitkyrka
force-pushed
the
vwhitchurch/keda-discovery
branch
3 times, most recently
from
July 17, 2026 13:53
d43155c to
ade09a4
Compare
vitkyrka
added a commit
that referenced
this pull request
Jul 24, 2026
Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vitkyrka
force-pushed
the
vwhitchurch/tekton-discovery
branch
from
July 24, 2026 08:37
9435620 to
167dbf0
Compare
vitkyrka
changed the base branch from
vwhitchurch/keda-discovery
to
vwhitchurch/velero-discovery
July 24, 2026 08:37
vitkyrka
force-pushed
the
vwhitchurch/tekton-discovery
branch
2 times, most recently
from
July 24, 2026 08:47
fc49944 to
e380c82
Compare
Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vitkyrka
force-pushed
the
vwhitchurch/tekton-discovery
branch
from
July 24, 2026 09:29
c7574be to
df9961d
Compare
Contributor
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
Validation ReportAll 21 validations passed. Show details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

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 nocontainerPorton the pod spec at all — the port is only exposed via a separately-created KubernetesServiceobject (confirmed both in the upstreamtektoncd/triggersrelease manifests and on a live cluster viakubectl 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 (which does declare acontainerPortnamedmetrics) is covered here.AD identifier: Tekton's official release images are built with
koand 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 thetektoncd/pipelinev1.0.0andv1.14.0GitHub release manifests — and is the exact image every real deployment applying the standard release YAML runs, so it's used verbatim as thead_identifiersvalue.Motivation
https://datadoghq.atlassian.net/browse/DSCVR-609
Review checklist (to be filled by reviewers)
qa/requiredif this PR needs QA validation, orqa/skip-qaif it does not. Exactly one of the two is required.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged