I wrote a Thunderbird add-on for my work computer that periodically exports my entire DTEX calendar to a file. Unfortunately, the file it creates is not directly usable by the kitchen screen server currently; it seems to use a time zone identifier that `tzinfo` doesn't understand: ``` Error in background update: Traceback (most recent call last): File "/usr/local/kitchen/lib64/python3.12/site-packages/kitchen/service/agenda.py", line 19, in _background_update await self._update() File "/usr/local/kitchen/lib64/python3.12/site-packages/kitchen/service/agenda.py", line 34, in _update calendar = await self.fetch_calendar( ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/kitchen/lib64/python3.12/site-packages/kitchen/service/caldav.py", line 39, in fetch_calendar return icalendar.Calendar.from_ical(r.text) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/kitchen/lib64/python3.12/site-packages/icalendar/cal.py", line 369, in from_ical _timezone_cache[component['TZID']] = component.to_tz() ^^^^^^^^^^^^^^^^^ File "/usr/local/kitchen/lib64/python3.12/site-packages/icalendar/cal.py", line 659, in to_tz return cls() ^^^^^ File "/usr/local/kitchen/lib64/python3.12/site-packages/pytz/tzinfo.py", line 190, in __init__ self._transition_info[0]) ~~~~~~~~~~~~~~~~~~~~~^^^ IndexError: list index out of range ``` It seems to work fine in Nextcloud, though, so the work-around is to import it as a subscription in Nextcloud and then read it from there, using Nextcloud as a sort of proxy. |
||
---|---|---|
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.