Repository navigation
Conversation
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
from
October 12, 2026 17:09
ed5cb75 to
72b9277
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
2 times, most recently
from
October 12, 2026 17:21
04be86e to
6dd0b2e
Compare
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
2 times, most recently
from
October 12, 2026 21:17
5881153 to
fca9c6a
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
from
October 12, 2026 21:17
5cb836e to
269968e
Compare
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
from
October 12, 2026 21:40
fca9c6a to
24cb1df
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
from
October 12, 2026 21:40
269968e to
15d99c3
Compare
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
from
October 12, 2026 22:05
24cb1df to
7da69df
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
from
October 12, 2026 22:05
15d99c3 to
1e1b0f6
Compare
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
from
October 12, 2026 22:07
7da69df to
4b2a716
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
from
October 12, 2026 22:07
1e1b0f6 to
7c45dd9
Compare
scotwells
force-pushed
the
test/internal-dns-distributed-qualification
branch
from
October 12, 2026 22:16
4b2a716 to
fb6a544
Compare
scotwells
force-pushed
the
fix/internal-dns-default-domain
branch
from
October 12, 2026 22:16
7c45dd9 to
0696098
Compare
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.
Summary
Allocate an independent private zone using the domain requested by a trusted consumer integration. DNS contexts keep records isolated when consumers use the same domain or overlapping addresses.
User experience
Network services requests
managedNamespace.domainSuffix: datum.internalfor the default VPC domain. DNS returns the allocated zone and suffix through context status. The requested domain is required when managed naming is enabled and is immutable within the context lifetime.Product publishers reserve labels directly in the allocated zone. Naming policies can add aliases in authorized zones.
Validation
All CI checks pass, including shared Kubernetes qualification.
Internal DNS tests, Kubernetes fixture tests, and CI-version lint pass locally. Kubernetes API tests verify domain validation and immutability. Allocation tests cover overlapping domains, custom domains, and distinct zone lifetimes. Kubernetes qualification covers isolated UDP and TCP answers for the same
web.datum.internalhostname. Guest-to-DNS qualification remains a release requirement.Stacked on #239. Supports datum-cloud/compute#451.