[Lab Notes] Kubernetes the Hard Way, For Real This Time (Step 04)
Continuing my Kubernetes the Hard Way homelab build on Proxmox. Steps 01-03 are already done, this covers step 04. Original guide: 04-certificate-authority.md Thoughts I had while doing this Before the actual step though, here are some stuff I learned or was thinking about along the way: Kubernetes is starting to feel like a miniaturized version of an entire IT infrastructure. Compute already got…
In the fourth step of the Kubernetes the Hard Way guide, the author completes the process of establishing the cluster's public key infrastructure (PKI). This involves generating and installing a self-signed Certificate Authority (CA) key and certificate, as well as key and certificate pairs for each Kubernetes component.
The author begins by generating the CA key and self-signed CA certificate using OpenSSL commands. After confirming the generated files, they proceed to generate a key, Certificate Signing Request (CSR), and signed certificate for each Kubernetes component in a loop. The components include admin, both worker nodes, kube-proxy, kube-scheduler, kube-controller-manager, kube-api-server, and service-accounts.
Once the certificates for all components are generated, the author confirms that the expected files have been created. Finally, they distribute the CA certificate and each component's certificate and key to the appropriate nodes. The controller node receives the CA, API server, and service-account key/cert pairs, while the worker nodes receive their respective certificates and keys.
With Step 04 completed, the cluster's PKI is now established, enabling secure communication between all Kubernetes components.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
