Kubernetes - kubeconfig
kubeconfig: contains info for clients (e.g.
kubectl by users,
kube-scheduler) to talk to api server. Can be found in
To check the current config:
$ kubectl config view
On admin node:
To talk to a different cluster:
$ kubectl --kubeconfig /path/to/kubeconfig
A config has multiple contexts.
kubeconfig is a
apiVersion: v1 kind: Config
TL;DR: context = a cluster + a user + a namespace (Each of the three is optional)
A context in Kubernetes is a group of access parameters. Each context contains a Kubernetes cluster, a user, and a namespace. The current context is the cluster that is currently the default for
kubectl commands run against that cluster. Each of the context that have been used will be available on your
A context is the connection to a specific cluster (username/apiserver host) used by kubectl.
"Context" only applies in the kubernetes client-side (where you run the
kubectl command); kubernetes server-side doesn't recognize the term 'context'.
# Show current context $ kubectl config current-context # Get all contexts $ kubectl config get-contexts
Stored as a Secret
kubeconfig may be stored as a