feat(kube): join the managed fleet config and notice when it moves - #4
Merged
Conversation
The fleet arrives as a generated file rather than as edits to ~/.kube/config, so it is joined through KUBECONFIG with the personal config first: a duplicate key resolves to the earlier file, which leaves hand-made entries behaving exactly as before. The drift check talks to a git remote, so it runs detached and the shell prints the previous run's answer. A slow or unreachable registry then costs a stale notice rather than a delayed prompt — the failure mode that would otherwise get the whole thing deleted from the profile. It reports and never applies: adding or removing a context silently changes where the next command lands. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: sanchpet <petrov@sanch.pet>
sanchpet
added a commit
that referenced
this pull request
Aug 18, 2026
The fleet arrives as a generated file rather than as edits to ~/.kube/config, so it is joined through KUBECONFIG with the personal config first: a duplicate key resolves to the earlier file, which leaves hand-made entries behaving exactly as before. The drift check talks to a git remote, so it runs detached and the shell prints the previous run's answer. A slow or unreachable registry then costs a stale notice rather than a delayed prompt — the failure mode that would otherwise get the whole thing deleted from the profile. It reports and never applies: adding or removing a context silently changes where the next command lands. Assisted-By: Claude <noreply@anthropic.com> Signed-off-by: sanchpet <petrov@sanch.pet>
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.
What
Joins a generated
~/.kube/tv-fleet.yamlontoKUBECONFIGwhen it exists, and prints a once-a-day notice when the cluster fleet has moved.Why
The fleet arrives as a whole generated file rather than as edits to
~/.kube/config, because a merge cannot remove — a decommissioned cluster would stay on the workstation forever, and a context pointing at something that is gone is worse than a missing one. Personal config comes first in the list, so on a duplicate key the hand-made entry wins and nothing existing changes behaviour.The drift check talks to a git remote, so it runs detached and the shell prints the previous run's answer. A slow or unreachable registry then costs a stale notice rather than a delayed prompt, which is the failure mode that gets this sort of thing deleted from a profile. It reports and never applies: silently adding or removing a context changes where the next command lands.
Verified on this machine: a cold run returns instantly and prints nothing, the background run leaves its answer, the next shell prints it, and after a sync the notice falls silent.
Assisted-By: Claude noreply@anthropic.com