Dustin C. Hatch
ce3bc87f9e
After considering the implications of Authelia's pre-configured consent feature, I decided I did not like the fact that a malicious program could potentially take over my entire Kubernetes cluster without my knowledge, since `kubectl` may not require any interaction, and could therefore be executed without my knowledge. I stopped ticking the "Remember Consent" checkbox out of paranoia, but that's gotten kind of annoying. I figure a good compromise is to only prompt for consent a couple of times per day.
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.