Dustin C. Hatch
e56526600d
Editing `configuration.yaml` et al. using `vi` via `kubectl exec` is rather tedious, since the version of `vi` in the *home-assistant* container image is very rudimentary. Thus, I think it would be better to use a ConfigMap to store the manually-edited YAML files, so I can edit them with my regular editor on my desktop. For this to work, the ConfigMap has to be mounted as a directory rather than as individual files (using `subPath`), as otherwise the pod would have to be restarted every time one of the files is updated.
Dustin's Kubernetes Cluster
This repository contains resources for deploying and managing my on-premises Kubernetes cluster
Cluster Setup
The cluster primarily consists of libvirt/QEMU+KVM virtual machines. The Control Plane nodes are VMs, as are the x86_64 worker nodes. Eventually, I would like to add Raspberry Pi or Pine64 machines as aarch64 nodes.
All machines run Fedora, using only Fedora builds of the Kubernetes components
(kubeadm, kubectl, and kubeadm).
See Cluster Setup for details.
Jenkins Agents
One of the main use cases for the Kubernetes cluster is to provide dynamic agents for Jenkins. Using the Kubernetes Plugin, Jenkins will automatically launch worker nodes as Kubernetes pods.
See Jenkins Kubernetes Integration for details.
Persistent Storage
Persistent storage for pods is provided by Longhorn. Longhorn runs within the cluster and provisions storage on worker nodes to make available to pods over iSCSI.
See Persistent Storage Using Longorn for details.