Dustin
42a7964991
I haven't fully determined why, but when the Music Assistant server restarts, it marks the _shairport-sync_ players as offline and will not allow playing to them. The only way I have found to work around this is to restart the players after the server restarts. As that's pretty cumbersome and annoying, I naturally want to automate it, so I've created this rudimentary synchronization technique using _ntfy_: each player listens for notifications on a specific topic, and upon receiving one, tells _shairport-sync_ to exit. With the `Restart=` property configured on the _shairport-sync.service_ unit, _systemd_ will restart the service, which causes Music Assistant to discover the player again. |
||
|---|---|---|
| 20125 | ||
| ansible | ||
| argocd | ||
| authelia | ||
| autoscaler | ||
| 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.