Running Jenkins in Kubernetes is relatively straightforward. The Kubernetes plugin automatically discovers all the connection and authentication configuration, so a `kubeconfig` file is no longer necessary. I did set the *Jenkins tunnel* option, though, so that agents will connect directly to the Jenkins JNLP port instead of going through the ingress controller. Jobs now run in pods in the *jenkins-job* namespace instead of the *jenkins* namespace. The latter is now where the Jenkins controller runs, and the controller should not have permission to modify its own resources. |
||
---|---|---|
autoscaler | ||
docker-distribution | ||
dynk8s-provisioner | ||
hudctrl | ||
ingress | ||
jenkins | ||
kitchen | ||
metrics | ||
phpipam | ||
prometheus_speedtest | ||
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.