Dustin C. Hatch
ee00412bf6
Usually, `xactfetch` will only fail for one bank or the other. Rarely do we want to redownload the data from both banks just because one failed. The latest version of `xactfetch` supports specifying a bank name as a CLI argument, so now we can define separate jobs for each bank. Then, when one Job fails, only that one will be retried later. It's kind of a bummer that it's so repetitive to define two CronJobs that differ by only a single command-line argument. I suppose that's a good argument for using one of the preprocessor tools like Jsonnet or KCL.
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.