From d1f7e159e129080745846eac287960b1a3b7c0d1 Mon Sep 17 00:00:00 2001 From: Kelsey Hightower Date: Tue, 8 Apr 2025 07:42:00 -0700 Subject: [PATCH] document control plane status checks --- docs/08-bootstrapping-kubernetes-controllers.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/08-bootstrapping-kubernetes-controllers.md b/docs/08-bootstrapping-kubernetes-controllers.md index 9840b5d..0d8c0ec 100644 --- a/docs/08-bootstrapping-kubernetes-controllers.md +++ b/docs/08-bootstrapping-kubernetes-controllers.md @@ -122,22 +122,22 @@ mv kube-scheduler.service /etc/systemd/system/ > Allow up to 10 seconds for the Kubernetes API Server to fully initialize. -You can check if the Kubernetes API Server is active by running the following command: +You can check if any of the control plane components are active using the `systemctl` command. For example, to check if the `kube-apiserver` fully initialized, and active, run the following command: ```bash systemctl is-active kube-apiserver ``` -For a more detailed status check run the following command: +For a more detailed status check, which includes additional process information and log messages, use the `systemctl status` command: ```bash systemctl status kube-apiserver ``` -If you run into any errors or want to view the logs run the following command: +If you run into any errors, or want to view the logs for any of the control plane components, use the `journalctl` command. For example, to view the logs for the `kube-apiserver` run the following command: ```bash -journalctl -u kube-apiserver --no-pager +journalctl -u kube-apiserver ``` ### Verification