docs: use default kubeconfig with k3s context name - #246
Merged
Conversation
Local kubectl access now standardizes on the default kubeconfig (~/.kube/config) with a context named k3s instead of a dedicated per-cluster kubeconfig file. The example becomes a merge fragment (current-context dropped so it cannot hijack an existing default), and the README documents the flatten-merge flow. Companion to makeitworkcloud/tfroot-libvirt#28.
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
Aligns kubectl onboarding with the pattern shipped in makeitworkcloud/tfroot-libvirt#28:
docs/kubeconfig.example.yaml: context renamedmakeitworkcloud-k3s→k3s;current-contextdropped so the file is a safe merge fragment (cannot hijack an existing default context).README.md### kubectl access: replaces the dedicated~/.kube/makeitworkcloud-k3s.yamlflow with a flatten-merge into the default~/.kube/config(backup +0600preserved), and updates verification commands to--context k3s/--context=k3s.Why
KUBECONFIGexports or per-cluster files.email/groupsclaims. No cluster impact.Validation
Docs-only; no manifests, Applications, or secrets touched — Argo CD sync scope unaffected. The documented merge and verification commands were executed against a scratch kubeconfig: merge adds
k3salongside existing contexts, preservescurrent-context, and resolveshttps://api.makeitwork.cloud+makeitworkcloud-oidc. The same flow was applied to a real workstation config and verified with a livekubectl --context=k3s auth whoami(Dex OIDC,makeitworkcloud:adminsgroup).