Repository navigation
Conversation
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
1 participant
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
Give Compute instances automatic private names in each attached VPC's
datum.internalzone. Users attach workloads to a network without choosing a DNS zone or maintaining address records.User experience
Names follow the instance lifetime and use
<allocated-instance-name>.datum.internal.Instance.status.dnsreports assigned hostnames and publication readiness per network. Application readiness does not remove an instance identity name.Publication requires a current VPC resolver context, a separately issued scoped grant, and live edge network observations. Records expire when observations stop. The
InternalDNSPublishingfeature gate defaults to disabled.Workload providers handle guest resolver delivery through the separate network services integration. Enablement requires project authorization, trusted grant provisioning, and read-only edge credentials. DNS domain allocation depends on datum-cloud/dns-operator#243.
Validation
make test, repository lint, publisher race tests, and the affected Compute package tests pass locally. Tests cover context identity, grant permissions, source and network lifetime changes, bounded renewal, and DNS status ownership. Guest-to-DNS qualification in the shared Kubernetes environment remains a release requirement.Refs datum-cloud/enhancements#921 and #470.