Skip to content

docs: use default kubeconfig with k3s context name #28

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xnoto merged 1 commit into from
Sep 13, 2026
Merged

docs: use default kubeconfig with k3s context name #28

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions KUBECTL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,8 @@
Normal kubectl access connects directly to `https://api.makeitwork.cloud` and
uses the Dex OIDC flow documented in the
[`kustomize-cluster` README](https://github.com/makeitworkcloud/kustomize-cluster#kubectl-access).
The context is named `k3s` and lives in the default kubeconfig
(`~/.kube/config`); do not create a dedicated per-cluster kubeconfig file.
The k3s API server's matching OIDC issuer, client ID, and claim configuration is
provisioned from `cloud-init/k3s/cloud_init.cfg`.

Expand Down
Loading