Difference between revisions of "Kubectl cluster-info"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
{{lowercase}} | {{lowercase}} | ||
[[kubectl cluster-info]] | [[kubectl cluster-info]] | ||
| + | kubectl cluster-info | grep "Kubernetes control plane" | ||
[[kubectl cluster-info --help]] | [[kubectl cluster-info --help]] | ||
Revision as of 18:37, 21 October 2023
kubectl cluster-info kubectl cluster-info | grep "Kubernetes control plane" kubectl cluster-info --help
Contents
Examples
kubectl cluster-info Kubernetes control plane is running at https://127.0.0.1:62581 CoreDNS is running at https://127.0.0.1:62581/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
kubectl cluster-info Kubernetes master is running at https://127.0.0.1:55000 KubeDNS is running at https://127.0.0.1:55000/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
kubectl cluster-info Kubernetes master is running at https://172.17.0.43:6443 KubeDNS is running at https://172.17.0.43:6443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
kubectl cluster-info Kubernetes master is running at https://10.172.0.1 CoreDNS is running at https://10.172.0.1/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy CoreDNS is running at https://10.172.0.1/api/v1/namespaces/kube-system/services/kube-dns-worker:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
EKS
kubectl cluster-info Kubernetes control plane is running at https://5E39D5104example0BB2E658.gr7.us-east-2.eks.amazonaws.com CoreDNS is running at https://7739D904example5C07D43CBB2E699.gr7.us-east-2.eks.amazonaws.com/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
kubectl cluster-info To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. Unable to connect to the server: dial tcp: lookup XXXXXXZZZZZYYYYY.gr7.us-east-2.eks.amazonaws.com: no such host
GKS
kubectl cluster-info W0704 13:23:33.066839 90028 gcp.go:120] WARNING: the gcp auth plugin is deprecated in v1.22+, unavailable in v1.25+; use gcloud instead. To learn more, consult https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. Error from server (Forbidden): services is forbidden: User "[email protected]" cannot list resource "services" in API group "" in the namespace "kube-system": requires one of ["container.services.list"] permission(s).
Minikube
kubectl cluster-info Kubernetes control plane is running at https://127.0.0.1:53438 CoreDNS is running at https://127.0.0.1:53438/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
Related
kubectl cluster-info dumpkubectl config viewkubectl versionkubectl get all -A- Default EKS installation
- Kubernetes API
See also
kubectl cluster-info, /api/kubectl config[view | get-contexts | current-context | get-clusters | set-context | set-credentials ], ~/.kube/config, kubectl config --help,kubectx, Kubernetes contexts,KUBECONFIG, kubectl --kubeconfig- Kubectl information commands:
cluster-info|view|pods|nodes|services|version|describe | logs
Advertising:
