Difference between revisions of "Kubectl get componentstatus (deprecated)"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
etcd-0 Healthy | etcd-0 Healthy | ||
| + | * https://github.com/kubernetes/kubernetes/pull/93570 | ||
== See also == | == See also == | ||
* {{k get}} | * {{k get}} | ||
| + | * {{K8s tr}} | ||
[[Category:Kubernetes]] | [[Category:Kubernetes]] | ||
Latest revision as of 10:23, 14 December 2023
kubectl get componentstatus Warning: v1 ComponentStatus is deprecated in v1.19+ NAME STATUS MESSAGE ERROR controller-manager Healthy ok scheduler Healthy ok etcd-0 Healthy
See also[edit]
kubectl get: [all|componentstatus | pods | apiservices | events|event|nodes|replicaset|services|svc|namespaces|hpa|secret | deployments | serviceaccounts | endpoints | daemonset | networkpolicy],kubectl get -h- K8s troubleshooting:
kubectl logs, kubectl top, kubectl get events -A, kubectl describe pod, Liveness, Readiness,Kubernetes events, Pulling image, OOMKilled, ProbeWarning, Reason,FailedScheduling,errImagePull, ImagePullBackOff, Kubelet conditions:MemoryPressure, DiskPressure, KubeletHasSufficientPID, KubeletReady, kubectl [ debug | attach | exec ] kubectl cluster-info dump, SimKube, KWOK
Advertising:
