Difference between revisions of "Kubectl cluster-info"
Jump to navigation
Jump to search
(→EKS) Tags: Mobile web edit, Mobile edit |
Tags: Mobile web edit, Mobile edit |
||
| Line 43: | Line 43: | ||
== Related commands == | == Related commands == | ||
* <code>[[kubectl cluster-info dump]]</code> | * <code>[[kubectl cluster-info dump]]</code> | ||
| − | * <code>[[kubectl config view]]</code> | + | * <code>[[kubectl config]]</code>, <code>[[kubectl config view]]</code> |
* <code>[[kubectl version]]</code> | * <code>[[kubectl version]]</code> | ||
Revision as of 18:37, 10 June 2022
EKS cluster:
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
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:
