Dustin C. Hatch
30cbc568d0
This manifest deploys the *ingress-nginx* controller, which is responsible for handing traffic from clients outside the cluster and routing it to the proper pods. I am using host network mode here to avoid having to have another proxy in front of the ingress controller, which would be required in NodePort mode. I looked at MetalLB briefly, but decided to avoid it for now. As with everything else in the Kubernetes world, it seems massively complex.
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.