From 4c9f657f1261c0aa844a859c3e9dd7358438517f Mon Sep 17 00:00:00 2001 From: xnoto Date: Sat, 12 Sep 2026 21:22:31 -0600 Subject: [PATCH] docs: use default kubeconfig with k3s context name Local access now standardizes on the default kubeconfig (~/.kube/config) with a context named k3s instead of a dedicated per-cluster kubeconfig file. The context name is client-side only; the apiserver authenticates the Dex-issued token's email/groups claims, so this has no cluster or state impact. --- KUBECTL.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/KUBECTL.md b/KUBECTL.md index aba57fb..9f85734 100644 --- a/KUBECTL.md +++ b/KUBECTL.md @@ -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`.