kubernetes: separate API access from endpoint ownership - #217
Merged
Conversation
Add a persistent TLS-passthrough node proxy and route node and workstation kubeconfigs through it while preserving the canonical TLS identity. Make bootstrap use direct control-plane addresses without requiring canonical DNS or CNI, and expose proxy, canonical endpoint, and networking health independently. Record the design as accepted ADR-014.
|
Too many files changed for review (111 files, 100 file limit). Bypass the limit by tagging |
Zariel
enabled auto-merge (squash)
August 31, 2026 19:24
Keep Katl responsible for health-gated local API VIP ownership, while routing is supplied separately through generic system extensions. Remove the private BIRD runtime, BGP schema and status surface, documentation, and obsolete VM fixtures.
Zariel
force-pushed
the
api-endpoint-ownership
branch
from
August 31, 2026 19:26
83e393b to
ec6388f
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
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
Why
API client access, backend selection, endpoint publication, and routing were coupled in one mechanism. Giving each concern a distinct owner keeps Katl’s supported path small and makes external routing an explicit extension concern.