Dustin
687775c595
The "cron" container has not been working correctly for some time. No background tasks are getting run, and this error is printed in the log every minute: > `Target class [db.schema] does not exist` It turns out, this is because of the way the PHP `artisan` tool works. It MUST be able to write to the code directory, apparently to build some kind of cache. There may be a way to cache the data ahead of time, but I haven't found it yet. For now, it seems the only way to make Laravel-based applications run in a container is to make the container filesystem mutable. |
||
|---|---|---|
| 20125 | ||
| ansible | ||
| argocd | ||
| authelia | ||
| autoscaler | ||
| calico | ||
| cert-manager | ||
| collectd | ||
| dch-root-ca | ||
| dch-webhooks | ||
| device-plugins | ||
| docker-distribution | ||
| dynk8s-provisioner | ||
| firefly-iii | ||
| fleetlock | ||
| grafana | ||
| home-assistant | ||
| hudctrl | ||
| ingress | ||
| invoice-ninja | ||
| jenkins | ||
| keepalived | ||
| keyserv | ||
| kitchen | ||
| kubelet-csr-approver | ||
| loki-ca | ||
| metrics | ||
| music-assistant | ||
| ntfy | ||
| paperless-ngx | ||
| photoframesvc | ||
| phpipam | ||
| postgresql | ||
| prometheus_speedtest | ||
| promtail | ||
| rabbitmq | ||
| receipts | ||
| rent-reminder | ||
| restic | ||
| restic-exporter | ||
| scanservjs | ||
| sealed-secrets | ||
| setup | ||
| ssh-host-keys | ||
| sshca | ||
| step-ca | ||
| storage | ||
| updatebot | ||
| vaultwarden | ||
| victoria-metrics | ||
| websites | ||
| xactfetch | ||
| xactmon | ||
| 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.