Files
nixos/manifests
root 2d874d3969
buildbot/nix-eval Build done. (1 warning)
buildbot/nix-build Build done.
fix: two observability bugs from initial deployment
Fix 1 - UnPoller 404 on UDM Pro:
  Remove :8443 from UP_UNIFI_DEFAULT_URL. UniFi OS devices (UDM Pro,
  UDM, UXG, CloudKey) use a different API path and do NOT use port 8443.
  URL should be https://10.42.1.1 (no port); unpoller handles the
  /proxy/network path internally for UniFi OS devices.

Fix 2 - Grafana dashboards showing invalid datasource:
  Add uid = "prometheus" to the provisioned Prometheus datasource.
  Without an explicit UID, Grafana auto-generates one on first run.
  All dashboard JSON references datasource uid "prometheus" which
  only works if the provisioning explicitly sets that UID.
2026-03-25 12:37:29 -05:00
..
2025-11-23 14:43:36 -06:00
2025-10-19 21:48:30 -05:00
2025-10-22 16:18:02 -05:00
2026-03-09 17:33:36 -05:00
2025-12-29 00:42:14 -06:00
2025-11-26 20:44:43 -06:00
2025-07-07 21:48:47 -05:00
2025-11-23 14:43:15 -06:00
2025-05-26 17:10:01 -05:00

Stands up my personal infrastructure in a Kubernetes environment.

First Thing First

In order to properly get things up and going, you will need to create a secret to allow the external secrets to log into BitWarden Password Manager. For obvious reasont this cannot be safely added to this repository. As such, it is suggested you create this manually.

kubectl create namespace bitwarden
kubectl create secret generic bitwarden-cli --namespace bitwarden --from-literal=BW_USERNAME=my_username --from-literal=BW_PASSWORD=my_password
# Alternative to the preceding line if you don't want the data in your shell history
kubectl create secret generic bitwarden-cli  --namespace bitwarden --from-file=./BW_USERNAME.txt --from-file=./BW_PASSWORD.txt
# And yet an entirely other option, if I'm logged into my own systems
sudo cat /run/agenix/bw_secret | kubectl apply -f -

Now Configure Cluster Services

To apply this you need to install kubectl, kustomize, and helm. It can then by applied by simply invoking the command:

# Working directory is assumed to be the manifests directory
./apply.sh

Once the basic cluster stuff is setup, you can just apply this directory with

kubectl apply -k .