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 |
Kubernetes control plane is running at https://127.0.0.1:62581 | 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 | [[CoreDNS]] is running at https://127.0.0.1:62581/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy | ||
Revision as of 14:09, 1 February 2022
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'.
Related commands
See also
- Kubectl information commands:
cluster-info|view|pods|nodes|services|version|describe | logs kubectl: [cp | config | create|delete|edit | explain |apply|exec|get|set|drain | uncordon | rolling-update|rollout|logs|run|auth|label | annotate|version|top|diff|debug|replace|describe|port-forward | proxy|scale|rollout|api-resources| expose deployment | expose | patch | attach | get endpoints | ~/.kube/config | kubectl logs --help | kubectl --help, kubectl-convert, kubectl autoscale, kubectl.kubernetes.io
Advertising:
