We're going to be using Longhorn for persistent storage. Longhorn allocates space on worker nodes and exposes iSCSI LUNs to other worker nodes. It creates sparse filesystem images under `/var/lib/longhorn` for each volume. Thus, we need to mount a large filesystem at that path on each worker node for Longhorn to use. Using two different kickstart scripts, one for the control plane nodes, and one for the worker nodes, we can properly mount the Longhorn data directory only on machines that will be running the Longhorn manager. Longhorn only supports *ext4* and *XFS* filesystem types. |
||
---|---|---|
jenkins | ||
setup | ||
README.md |
README.md
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.