From ea9178edae6ce04895fdc37e32433b4d2a7825fa Mon Sep 17 00:00:00 2001
From: Kelsey Hightower <kelsey.hightower@gmail.com>
Date: Mon, 7 Apr 2025 17:08:56 -0700
Subject: [PATCH] set kubelet hostname

---
 docs/03-compute-resources.md                  | 11 ++++++-----
 ...08-bootstrapping-kubernetes-controllers.md | 19 +++++++++++++++++++
 docs/09-bootstrapping-kubernetes-workers.md   | 10 ++++++++++
 3 files changed, 35 insertions(+), 5 deletions(-)

diff --git a/docs/03-compute-resources.md b/docs/03-compute-resources.md
index 81d341f..05ee6cc 100644
--- a/docs/03-compute-resources.md
+++ b/docs/03-compute-resources.md
@@ -105,9 +105,10 @@ Set the hostname on each machine listed in the `machines.txt` file:
 
 ```bash
 while read IP FQDN HOST SUBNET; do
-    CMD="sed -i 's/^127.0.0.1.*/127.0.0.1\t${FQDN} ${HOST} localhost/' /etc/hosts"
+    CMD="sed -i 's/^127.0.1.1.*/127.0.1.1\t${FQDN} ${HOST}/' /etc/hosts"
     ssh -n root@${IP} "$CMD"
-    ssh -n root@${IP} hostnamectl hostname ${HOST}
+    ssh -n root@${IP} hostnamectl set-hostname ${HOST}
+    ssh -n root@${IP} systemctl restart systemd-hostnamed
 done < machines.txt
 ```
 
@@ -199,9 +200,9 @@ done
 ```
 
 ```text
-server aarch64 GNU/Linux
-node-0 aarch64 GNU/Linux
-node-1 aarch64 GNU/Linux
+server.kubernetes.local aarch64 GNU/Linux
+node-0.kubernetes.local aarch64 GNU/Linux
+node-1.kubernetes.local aarch64 GNU/Linux
 ```
 
 ## Adding `/etc/hosts` Entries To The Remote Machines
diff --git a/docs/08-bootstrapping-kubernetes-controllers.md b/docs/08-bootstrapping-kubernetes-controllers.md
index 1378ab4..28e5ca1 100644
--- a/docs/08-bootstrapping-kubernetes-controllers.md
+++ b/docs/08-bootstrapping-kubernetes-controllers.md
@@ -122,9 +122,28 @@ 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:
+
+```bash
+systemctl is-active kube-apiserver
+```
+
+For a more detailed status check run the following command:
+
+```bash
+systemctl status kube-apiserver
+```
+
+If you run into any errors or want to view the logs run the following command:
+
+```bash
+journalctl -u kube-apiserver --no-pager
+```
 
 ### Verification
 
+At this point the Kubernetes control plane components should be up and running. Verify this using the `kubectl` command line tool:
+
 ```bash
 kubectl cluster-info \
   --kubeconfig admin.kubeconfig
diff --git a/docs/09-bootstrapping-kubernetes-workers.md b/docs/09-bootstrapping-kubernetes-workers.md
index 38a619a..5cab730 100644
--- a/docs/09-bootstrapping-kubernetes-workers.md
+++ b/docs/09-bootstrapping-kubernetes-workers.md
@@ -156,6 +156,16 @@ Create the `kubelet-config.yaml` configuration file:
 }
 ```
 
+Check if the kubelet service is running:
+
+```bash
+systemctl is-active kubelet
+```
+
+```text
+active
+```
+
 Be sure to complete the steps in this section on each worker node, `node-0` and `node-1`, before moving on to the next section.
 
 ## Verification