差異處

這裏顯示兩個版本的差異處。

--- tech:kubectl [2025/12/06 11:41] – 刪除 PVC 後一直在 Terminating 狀態 jonathan
+++ tech:kubectl [2025/12/06 11:57] (目前版本) – [檢查 K8s Cluster 的健康狀態] jonathan
@@ 行 6: / 行 6: @@
 ===== 檢查 K8s Cluster 的健康狀態 =====
-  * 參考 - https://stackoverflow.com/questions/54882727/kubectl-using-command-to-get-cluster-status
+  * 檢查 API server<cli>
-  * <cli>kubectl get componentstatus</cli>結果類似以下訊息:<cli>
+kubectl get --raw='/healthz?verbose'
-$ kubectl get componentstatus
-NAME                 STATUS    MESSAGE             ERROR
-controller-manager   Healthy   ok
-scheduler            Healthy   ok
-etcd-0               Healthy   {"health":"true"}
 </cli>
+    * ++看實際執行結果|<cli>
+jonathan@k3s-master-171:~$ kubectl get --raw='/healthz?verbose'
+[+]ping ok
+[+]log ok
+[+]etcd ok
+[+]poststarthook/start-apiserver-admission-initializer ok
+[+]poststarthook/generic-apiserver-start-informers ok
+[+]poststarthook/priority-and-fairness-config-consumer ok
+[+]poststarthook/priority-and-fairness-filter ok
+[+]poststarthook/storage-object-count-tracker-hook ok
+[+]poststarthook/start-apiextensions-informers ok
+[+]poststarthook/start-apiextensions-controllers ok
+[+]poststarthook/crd-informer-synced ok
+[+]poststarthook/start-system-namespaces-controller ok
+[+]poststarthook/start-cluster-authentication-info-controller ok
+[+]poststarthook/start-kube-apiserver-identity-lease-controller ok
+[+]poststarthook/start-kube-apiserver-identity-lease-garbage-collector ok
+[+]poststarthook/start-legacy-token-tracking-controller ok
+[+]poststarthook/start-service-ip-repair-controllers ok
+[+]poststarthook/rbac/bootstrap-roles ok
+[+]poststarthook/scheduling/bootstrap-system-priority-classes ok
+[+]poststarthook/priority-and-fairness-config-producer ok
+[+]poststarthook/bootstrap-controller ok
+[+]poststarthook/start-kubernetes-service-cidr-controller ok
+[+]poststarthook/aggregator-reload-proxy-client-cert ok
+[+]poststarthook/start-kube-aggregator-informers ok
+[+]poststarthook/apiservice-status-local-available-controller ok
+[+]poststarthook/apiservice-status-remote-available-controller ok
+[+]poststarthook/apiservice-registration-controller ok
+[+]poststarthook/apiservice-discovery-controller ok
+[+]poststarthook/kube-apiserver-autoregistration ok
+[+]autoregister-completion ok
+[+]poststarthook/apiservice-openapi-controller ok
+[+]poststarthook/apiservice-openapiv3-controller ok
+healthz check passed
+</cli>++
+  * 檢查 etcd<cli>
+kubectl get --raw='/healthz/etcd'
+</cli>
+    * ++看實際執行結果|<cli>
+jonathan@k3s-master-171:~$ kubectl get --raw='/healthz/etcd'
+ok
+</cli>++
+  * 檢查 kube-system <cli>
+kubectl get pods -n kube-system
+</cli>
+    * ++看實際執行結果|<cli>
+jonathan@k3s-master-171:~$ kubectl get pods -n kube-system
+NAME                                      READY   STATUS    RESTARTS       AGE
+coredns-64fd4b4794-28wrz                  1/1     Running   1 (5d1h ago)   11d
+local-path-provisioner-774c6665dc-t8g2l   1/1     Running   1 (5d1h ago)   11d
+metrics-server-7bfffcd44-5mkbj            1/1     Running   2 (5d1h ago)   11d
+</cli>++
 ===== 讀取 K8s Cluster Name 的方式 =====
@@ 行 144: / 行 192: @@
 ===== 顯示 K8s 內的 deploy 清單 =====
-  * <cli>kubctl get deploy</cli> Exp.<cli>
+  * <cli>kubectl get deploy</cli> Exp.<cli>
 localadmin@iiidevops-73:~$ kubectl get deploy
 NAME                 READY   UP-TO-DATE   AVAILABLE   AGE
@@ 行 164: / 行 212: @@
 ===== 顯示 K8s 內的 namespace 清單 =====
-  * <cli>kubctl get namespace </cli> Exp.<cli>
+  * <cli>kubectl get namespace </cli> Exp.<cli>
 iiidevops@iiidevops1:~$ kubectl get namespace
 NAME                   STATUS   AGE