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.
Document how the DNS64 prototype uses internal service resources, node-local bidirectional routing, and routing metrics and logs. Clarify cleanup and rollback limits and the planned readiness agreement between the resolver VIP, Galactic route, and shared NAT64 prefix. Keep the product diagrams unchanged.
The document describes the current prototype and its limitations. It explicitly states that cross-node routing and health-based withdrawal are not implemented and production DNS64/NAT64 packet-path validation is incomplete. The prototype is not production-ready.
Validation: Markdown lint, reference/local-link checks,
git diff --check, andgo test ./internal/serviceroutepass.task cistops during eBPF generation becausellvm-stripis missing locally.Related: Galactic routing #634, Galactic observability #635, Network API #27.