Dustin C. Hatch 5b34547730 h-a: Config Zigbee2MQTT w/ env vars
Zigbee2MQTT commits the cardinal sin of storing state in its
configuration file.  This means the file has to be writable and thus
stored in persistent storage rather than in a ConfigMap.  As a
consequence, making changes to the configuration when the application is
not running is rather difficult.  Case in point: when I added the
internal alias for _mqtt.pyrocufflink.blue_ pointing to the in-cluster
service, Zigbee2MQTT became unable to connect to the broker because it
was using the node port instead of the internal port.  Since it could
not connect to the broker, it refused to start, and thus the container
would not stay running long enough to fix the configuration to point
to the correct port.

Fortunately, Zigbee2MQTT also allows configuring settings via
environment variables, which can be managed with a ConfigMap.  Luckily,
the values read from environment variables override those from the
configuration file, so pointing to the correct broker port with the
environment variable was sufficient to allow the application to start.
2024-08-01 09:27:52 -05:00
2024-02-22 07:10:01 -06:00
2022-12-18 16:26:07 -06:00
2024-07-26 20:59:00 -05:00
2024-07-04 06:53:58 -05:00
2024-05-26 11:48:12 -05:00
2024-06-06 11:03:42 -05:00
2023-10-14 07:28:05 -05:00
2023-10-19 07:12:16 -05:00
2024-02-22 07:10:01 -06:00
2024-07-26 20:59:00 -05:00
2023-07-08 07:06:10 -05:00
2024-07-27 13:07:26 -05:00
2024-07-26 20:53:19 -05:00
2022-07-31 01:38:46 -05:00

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.

Description
Resources for deploying and managing my personal Kubernetes cluster
Readme 3.9 MiB
Languages
Shell 80.5%
JavaScript 17.2%
Awk 2.3%