infra
/
kubernetes
1
0
Fork 0
Code Pull Requests 4 Activity
Resources for deploying and managing my personal Kubernetes cluster
62 Commits
9 Branches
0 Tags
3.5 MiB
Shell 83.2%
JavaScript 14.8%
Awk 2%
 
 
 
Go to file
Dustin c5d0052ed3 cert-manager: Add DNS.01 solver using Cloudflare 
Using *acme-dns.io* is incredibly cumbersome.  Since each unique
subdomain requires its own set of credentials, the `acme-dns.json` file
has to be updated every time a new certificate is added.  This
effectively precludes creating certificates via Ingress annotations.

As Cloudflare's DNS service is free and anonymous as well, I thought I
would try it out as an alternative to *acme-dns.io*.  It seems to work
well so far.  One potential issue, though, is Cloudflare seems to have
several nameservers, with multiple IP addresses each.  This may require
adding quite a few exceptions to the no-outbound-DNS rule on the
firewall.  I tried using the "recursive servers only" mode of
*cert-manager*, however, as expected, the recursive servers all cache
too aggressively.  Since the negative cache TTL value in the SOA record
for Cloudflare DNS zones is set to 1 hour and cannot be configured, ACME
challenges can take at least that long in this mode.  Thus, querying the
authoritative servers directly is indeed the best option, even though it
violates the no-outbound-DNS rule.
 		2023-05-09 21:13:08 -05:00
authelia authelia: Set OIDC consent duration 2023-04-23 15:56:50 -05:00
autoscaler autoscaler: Tolerate control-plane taint 2022-12-16 17:20:22 -06:00
cert-manager cert-manager: Add DNS.01 solver using Cloudflare 2023-05-09 21:13:08 -05:00
docker-distribution docker-distribution: Deploy OCI image registry 2022-07-31 01:15:01 -05:00
dynk8s-provisioner dynk8s: Fix Ingress routing 2022-11-24 11:14:01 -06:00
hudctrl hudctrl: Update for v0.2.0 2022-12-18 16:26:07 -06:00
ingress ingress: Show how to import cert as secret 2022-08-23 21:20:47 -05:00
jenkins jenkins: Remove dockerconfigjson 2022-12-28 11:05:40 -06:00
kitchen kitchen: Allow Jenkins to restart deployment 2022-11-06 17:22:46 -06:00
metrics metrics: Add role to allow anon access to metrics 2022-11-05 16:23:02 -05:00
ntfy ntfy: Allow notification attachments 2023-01-13 09:41:10 -06:00
paperless-ngx paperless-ngx: Deploy application 2023-01-13 21:33:14 -06:00
phpipam phpipam: Update to v1.5.2 2023-04-20 13:59:30 -05:00
prometheus_speedtest prom_speedtest: Add application manifest 2022-08-06 22:21:06 -05:00
scanservjs scanservjs: ingress: Increase proxy read timeout 2023-04-20 17:40:58 -05:00
setup setup: ks: Generate iSCSI initiator name 2022-08-23 21:22:01 -05:00
storage storage: Upgrade Longhorn to v1.4.1 2023-04-24 23:21:55 -05:00
README.md README: Add storage section 2022-07-31 01:38:46 -05:00

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.