Using the local name server as the authoritative server for ACME challenge records turned out to be quite problematic. For some reason, both Google and Cloudflare kept returning SERVFAIL responses for the *_acme-challenge* TXT queries. I suspect this may have had something to do with how BIND was configured to be the authoritative server for the *o-ak4p9kqlmt5uuc.com* while also being a recusive resolver for clients on the local network. Using *acme-dns.io* resolves these issues, but it does bring a few of its own. Notably, each unique domain and subdomain must have its own set of credentials (specified in the `acme-dns.json`) file. This makes adding new certificates rather cumbersome. |
||
---|---|---|
authelia | ||
autoscaler | ||
cert-manager | ||
docker-distribution | ||
dynk8s-provisioner | ||
hudctrl | ||
ingress | ||
jenkins | ||
kitchen | ||
metrics | ||
ntfy | ||
paperless-ngx | ||
phpipam | ||
prometheus_speedtest | ||
scanservjs | ||
setup | ||
storage | ||
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.
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.