Dustin C. Hatch
81266d4ef9
Having the Z-Wave and Zigbee admin interfaces exposed as sub-paths under *homeassistant.pyrocufflink.blue* made it difficult to use Authelia. Since I have a Firefox container tab specifically for Home Assistant, the login redirect would open a new tab in a different container, since Authelia is hosted at *auth.pyrocufflink.blue*. In order to log in, I would have to temporarily disable "designated sites only" for the Home Assistant tab container. Using subdomains for the admin interfaces avoids this issue, since I can use a different container for them, one that does not have the "designated sites only" setting, since I am less worried about accidentally leaking data to sites on the Internet from them.
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.