Dustin C. Hatch
721edd0d59
Without `disableNameSuffixHash` enabled, Kustomize will create a unique ConfigMap any time the contents of source file change. It will also update any Deployment, StatefulSet, etc resources to point to the new ConfigMap. This has the effect of restarting any pods that refer to the ConfigMap whenever its contents change. I had avoided using this initially because Kustomize does *not* delete previous ConfigMap resources whenever it creates a new one. Now that we have Argo CD, though, this is not an issue, as it will clean up the old resources whenever it synchronizes.
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.