Dustin C. Hatch
0965148f93
At some point, Firefly III added an `ALLOW_WEBHOOKS` option. It's set to `false` by default, but it didn't seem to have any affect on _running_ webhooks, only visiting the webhooks configuraiton page. Now, that seems to have changed, and the setting needs to be enabled in order for the webhooks to run. I'm not sure why `disableNameSuffixHash` was set on the ConfigMap generator. It shouldn't be, so that Kustomize can ensure the Pod is restarted when the contents of the ConfigMap change.
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.