Dustin C. Hatch
10ee364612
When cloning/fetching a Git repository in a Jenkins pipeline, the Git Client plugin uses the configured *Host Key Verification Strategy* to verify the SSH host key of the remote Git server. Unfortunately, there does not seem to be any way to use the configured strategy from the `git` command line in a Pipeline job, so e.g. `git push` does not respect it. This causes jobs to fail to push changes to the remote if the container they're using does not already have the SSH host key for the remote in its known hosts database. This commit adds a ConfigMap to the *jenkins-jobs* namespace that can be mounted in containers to populate the SSH host key database.
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.