boundary: add container-based config discovery support#24494
Draft
vitkyrka wants to merge 1 commit into
Draft
Conversation
vitkyrka
added
the
qa/skip-qa
vitkyrka
added a commit
that referenced
this pull request
Jul 10, 2026
Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Contributor
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 37d9a8f | Docs | Datadog PR Page | Give us feedback! |
vitkyrka
added a commit
that referenced
this pull request
Jul 13, 2026
Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vitkyrka
force-pushed
the
boundary-config-discovery
branch
from
July 13, 2026 15:36
7e16b34 to
e4b105b
Compare
vitkyrka
changed the base branch from
graphite-base/24494
to
vwhitchurch/docker-run-env-vars-e2e
July 13, 2026 15:36
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. |
This was referenced Jul 13, 2026
dd-octo-sts
Bot
added
dev/tooling
dev_package
and removed
dev/tooling
dev_package
labels
vitkyrka
force-pushed
the
vwhitchurch/docker-run-env-vars-e2e
branch
from
July 14, 2026 09:55
f3908fc to
3251f62
Compare
vitkyrka
added a commit
that referenced
this pull request
Jul 14, 2026
Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vitkyrka
force-pushed
the
boundary-config-discovery
branch
from
July 14, 2026 09:56
df1b43d to
fe66319
Compare
3 tasks
vitkyrka
marked this pull request as ready for review
July 14, 2026 12:55
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fe66319194
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
3 tasks
vitkyrka
force-pushed
the
boundary-config-discovery
branch
from
July 14, 2026 14:24
fe66319 to
9c74e94
Compare
vitkyrka
changed the base branch from
vwhitchurch/docker-run-env-vars-e2e
to
graphite-base/24494
July 14, 2026 14:28
Adds a from_ports discovery strategy that populates both health_endpoint and openmetrics_endpoint from the discovered container's port 9203, plus an auto_conf.yaml ad_identifiers entry matching the hashicorp/boundary image. Wires get_e2e_discovery_metadata into the E2E fixture, and adds test_e2e_discovery and test_e2e_discovery_all_candidates. Environment: Datadog workspace Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
vitkyrka
force-pushed
the
graphite-base/24494
branch
from
July 14, 2026 14:30
3251f62 to
f4762a7
Compare
vitkyrka
force-pushed
the
boundary-config-discovery
branch
from
July 14, 2026 14:30
9c74e94 to
37d9a8f
Compare
vitkyrka
changed the base branch from
graphite-base/24494
to
vwhitchurch/docker-run-env-vars-e2e
July 14, 2026 14:30
jeff-morgan-dd
approved these changes
Jul 14, 2026
Contributor
Validation ReportAll 21 validations passed. Show details
|
vitkyrka
marked this pull request as draft
July 15, 2026 09:58
vitkyrka
changed the base branch from
vwhitchurch/docker-run-env-vars-e2e
to
graphite-base/24494
July 17, 2026 09:55
3 tasks
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
2 participants
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 boundary.
Discovery stability log pattern: the container's audit event sink continuously retries writing to the host-owned log file bind-mounted at
/var/log/boundary/events.ndjson, which the container's non-rootboundaryprocess user can't write to (a pre-existing fixture limitation, unrelated to this change). This produces several differently-worded, benign[ERROR]log lines during every discovery candidate probe, sotest_e2e_discovery_all_candidatesuses aDISCOVERY_STABILITY_LOG_PATTERNSlist that drops the genericerrorpattern in favor of the more specific crash indicators (panic,fatal, etc.), following the same precedent used for milvus.Port selection rationale: Port 9203 is Boundary's
opslistener, which serves both the/healthand/metricsendpoints and is documented as the listener purpose dedicated to health checks and Prometheus metrics.Motivation
DSCVR-490.
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