Commit Graph
100 Commits
Author SHA1 Message Date
Ruben Hensen e95d78e160 docs: tick off microk8s 1.35
v1.35.6 with containerd 2.1.6. containerd converted the old config without warnings, and the fixed hosts.toml now parses.
2026-10-23 22:29:32 +02:00
Ruben Hensen b60d3b5589 docs: record the VACUUM and prepare microk8s 1.35
The database went from 709 MB to 44 MB, the first snapshot after it is 8.3 MB instead of 150 MB, and k8s-dqlite uses 403 MB instead of 1,346 MB.
2026-10-23 22:21:46 +02:00
Ruben Hensen 175769d36c Add a tool to VACUUM the k8s-dqlite database
dqlite supports VACUUM from v1.18.2, which microk8s 1.34 ships, but the dqlite shell wraps every statement in a transaction and SQLite refuses to VACUUM inside one. dqlite-vacuum sends it through the go-dqlite driver instead and otherwise just prints page statistics. dqlite-vacuum.sh makes the backups first.

Rehearsed on opti1 on a throwaway node in /dev/shm: 657 MB to 41 MB in 0.6s, with concurrent writes unaffected and the data intact after restarts.
2026-10-23 22:03:30 +02:00
Ruben Hensen c55b7ceab5 docs: tick off microk8s 1.34
v1.34.9 runs with the dqlite snapshot tuning intact. LIST latency is unchanged from 1.33, so the ConsistentListFromCache stalls of canonical/microk8s#5568 don't show here.
2026-10-23 21:42:44 +02:00
Ruben Hensen 67abb0b972 docs: prepare the move to microk8s 1.34
k8s-dqlite v1.8.1 in microk8s 1.34 already bundles dqlite 1.18.2, so the database can be vacuumed from 1.34 on. Also notes the containerd 2 jump at 1.35, the feature gates the 1.34 hook adds for kine, and the front-proxy certificate that expired in 2025.
2026-10-23 21:35:16 +02:00
Ruben Hensen a07ef664cb docs: tick off the Envoy Gateway migration 2026-10-23 21:29:37 +02:00
Ruben Hensen 0a810817b6 gatus: expect the authentik redirect for Longhorn
Longhorn now sits behind an authentik login on the Gateway instead of nginx basic auth, so the check expects a 302 without following it. Same change for s1 on node001.
2026-10-23 21:24:00 +02:00
Ruben Hensen 1f04831a97 Replace the Ingresses with Certificate resources
ingress-nginx is gone and every app is served by the Envoy Gateway. The certificates were created by cert-manager's ingress-shim and are owned by the Ingresses, so each app now declares its Certificate itself, with the same name, secret and usages, so nothing gets reissued. gateway-shim can't take over because the certificates live in the app namespaces.

immich drops mbg.hensen.io, which has no route, so that one certificate is reissued through the Gateway's HTTP-01 solver.

Also removes the Longhorn test-port redirect URI and updates comments that still described nginx.
2026-10-23 21:20:25 +02:00
Ruben Hensen 48f5c7d894 docs: tick off the switch to Envoy Gateway and the Longhorn login 2026-10-23 21:17:04 +02:00
Ruben Hensen 910b792452 longhorn: log in through authentik on the Gateway
Longhorn has no users of its own; nginx guarded it with basic auth using apr1 hashes, which Envoy Gateway does not support. An Envoy Gateway SecurityPolicy now sends visitors through an authentik OIDC application that only admins may use. The client secret lives in Vault at kv/longhorn-oidc and reaches both authentik and Envoy through External Secrets.
2026-10-23 21:07:31 +02:00
Ruben Hensen 009b8ce510 gateway: take over ports 80 and 443 from ingress-nginx
Envoy moves from the test ports to 80 and 443, and Let's Encrypt HTTP-01 challenges go through an HTTPRoute on the Gateway. Push only after sudo microk8s disable ingress, since both want the same host ports.
2026-10-23 21:02:52 +02:00
Ruben Hensen 23aaf5ab26 docs: tick off the routes and note what the switch-over needs 2026-10-23 21:02:10 +02:00
Ruben Hensen b360483210 cert-manager: enable the Gateway API integration
Needed for HTTP-01 challenges through the Gateway after the switch from ingress-nginx. Nothing changes until an issuer uses a gatewayHTTPRoute solver.
2026-10-23 21:01:17 +02:00
Ruben Hensen 134774509d argocd: serve plain HTTP behind the ingress and the Gateway
With server.insecure, TLS ends at nginx or Envoy and argocd-server serves plain HTTP, which is how Argo CD documents the Gateway API setup. The nginx Ingress now talks HTTP to the http port; the ssl-passthrough annotation did nothing without the controller flag. argocd-folder diffs server-side for the new HTTPRoute.
2026-10-23 17:44:08 +02:00
Ruben Hensen 69a0661d09 Add HTTPRoutes for the apps behind ingress-nginx
Each app gets an HTTPS listener on the Gateway with its existing certificate, an HTTPRoute, and a ReferenceGrant for that certificate. The routes drop Envoy's 15s request timeout, as nginx has no overall limit either. Argo CD and Longhorn follow separately; the Ingresses stay until the switch-over.
2026-10-23 17:39:04 +02:00
Ruben Hensen d1efb91a4b gateway: diff the Gateway resources server-side
The API server fills in Gateway API defaults such as the parentRef group and kind and a PathPrefix / match, so Argo CD's client-side diff kept gateway-folder OutOfSync.
2026-10-23 17:36:14 +02:00
Ruben Hensen f4377616e6 gatus: serve s2.rubenhensen.nl through the Gateway as well
First app on the Gateway API: an HTTPS listener for s2.rubenhensen.nl using the existing certificate in the gatus namespace, an HTTPRoute, and a ReferenceGrant for the certificate. Plain HTTP on the Gateway now redirects to HTTPS. The Ingress stays until the switch-over.
2026-10-23 17:30:42 +02:00
Ruben Hensen 8e508080d7 docs: plan the Envoy Gateway phases
Phase 1 is done: Envoy Gateway runs next to ingress-nginx on test ports.
2026-10-23 17:27:49 +02:00
Ruben Hensen 7475199ca5 gateway: add the Envoy GatewayClass and Gateway
Envoy runs as a DaemonSet on host ports 10080 and 10443 for now, so it can be tested next to ingress-nginx, which keeps 80 and 443. The Gateway has a plain HTTP listener and no routes yet.
2026-10-23 17:27:02 +02:00
Ruben Hensen a20808b752 envoy-gateway: install v1.9.2 next to ingress-nginx
First step of the move from the retired ingress-nginx to the Gateway API. This installs the controller with the Gateway API and Envoy Gateway CRDs. No Gateway exists yet, so no traffic changes.
2026-10-23 17:25:20 +02:00
Ruben Hensen 3a250b65cc docs: tick off cert-manager 1.21.2 2026-10-23 17:22:22 +02:00
Ruben Hensen 43a62ff48f cert-manager: upgrade to v1.21.2
1.21 supports Kubernetes 1.33 to 1.36. The chart no longer creates the tokenrequest Role and RoleBinding; nothing uses them, as the only issuer is ACME with HTTP-01 and no serviceAccountRef.
2026-10-23 17:20:15 +02:00
Ruben Hensen 2c4164ad22 velero: skip emptyDir volumes in scheduled backups
The nightly backup of 2026-10-23 ended PartiallyFailed because a repository maintenance job pod finished while Velero was reading its emptyDir volumes. emptyDir holds nothing worth restoring, so a volume policy now skips it for both schedules.
2026-10-23 17:12:12 +02:00
Ruben Hensen 336c37ca50 docs: tick off microk8s 1.33
The node runs v1.33.13 (snap revision 9067). kubelite logs the #5057 message but has not panicked or restarted, and the dqlite snapshot tuning carried over.
2026-10-23 17:06:27 +02:00
Ruben Hensen 5427666ff9 longhorn: list Argo CD's pre-delete finalizers
Argo CD 3.x adds pre-delete-finalizer.argocd.argoproj.io and its /cleanup variant to Applications with PreDelete hooks, which the Longhorn chart has. With only resources-finalizer in git, the apps app-of-apps stayed OutOfSync on helm-longhorn.
2026-10-23 17:03:32 +02:00
Ruben Hensen c3830cd9d7 docs: tick off the dqlite snapshot tuning
Over the first 40 minutes after the restart: snapshots 24.7 minutes apart instead of ~3, none of 9,445 lease updates took over 4s, and neither the CNPG operator nor the snapshot-controller restarted.
2026-10-23 00:53:11 +02:00
Ruben Hensen 6a782ff174 docs: plan the route to Kubernetes 1.36
1.34 brings the reworked k8s-dqlite write path, 1.36 a dqlite that can VACUUM the mostly empty datastore. Lists the per-hop checks, the one-way schema migration at 1.34, the components that still need to move for 1.35/1.36, and the staged dqlite tuning script on opti1.
2026-10-23 00:11:27 +02:00
Ruben Hensen 6508335914 docs: diagnose the k8s-dqlite write stalls
The dqlite SQLite file is ~709 MB with 95% free pages, so every 1,024 commits dqlite writes a ~150 MB snapshot that stalls commits for seconds and makes controllers lose leader election. Plan: larger snapshot threshold in tuning.yaml now, microk8s 1.34+ for the real fix.
2026-10-23 00:04:41 +02:00
Ruben Hensen 69edd7ef4c docs: tick off Calico 3.29.3, note the dqlite latency 2026-10-22 23:49:05 +02:00
Ruben Hensen 01470a260c docs: tick off Argo CD 3.4.12 2026-10-22 23:39:14 +02:00
Ruben Hensen f174ddee8f argocd: upgrade to v3.4.12
One minor at a time from v2.14.2 to v3.4.12, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:31:54 +02:00
Ruben Hensen 62043940e8 argocd: upgrade to v3.3.18
One minor at a time from v2.14.2 to v3.4.12, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:25:46 +02:00
Ruben Hensen 8a60dbc5ea argocd: sync Argo CD itself with server-side apply
Required from 3.3, whose ApplicationSet CRD no longer fits the last-applied annotation of client-side apply. Turned on while still on 3.2 so the managed-field migration happens before the CRD grows.
2026-10-22 23:25:28 +02:00
Ruben Hensen f9111bd17b argocd: upgrade to v3.2.12
One minor at a time from v2.14.2 to v3.4.12, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:20:57 +02:00
Ruben Hensen 0e6e9dc323 argocd: upgrade to v3.1.16
One minor at a time from v2.14.2 to v3.4.12, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:17:51 +02:00
Ruben Hensen 288714af21 argocd: upgrade to v3.0.23
One minor at a time from v2.14.2 to v3.4.12, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:14:17 +02:00
Ruben Hensen 66debf1e3c argocd: keep label-based resource tracking explicitly
Argo CD 3.0 switches the default to annotation tracking. Per the 2.14->3.0
upgrade notes, a resource whose first sync after the switch is a deletion
gets orphaned instead of pruned. Pinning label tracking (the 2.14 default,
so no change today) keeps the upgrade to 3.x free of that; moving to
annotations can follow once everything runs 3.4.
2026-10-22 23:13:11 +02:00
Ruben Hensen 108455de9c docs: tick off External Secrets 2.13.0 2026-10-22 23:07:32 +02:00
Ruben Hensen 69444a4ac0 external-secrets: upgrade to 2.13.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 23:03:25 +02:00
Ruben Hensen 30bc62a453 external-secrets: upgrade to 2.12.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:59:28 +02:00
Ruben Hensen 2b7b1799a4 external-secrets: upgrade to 2.11.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:55:59 +02:00
Ruben Hensen 00de7483d4 external-secrets: upgrade to 2.10.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:52:12 +02:00
Ruben Hensen bde9245497 external-secrets: upgrade to 2.9.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:48:24 +02:00
Ruben Hensen c2bece55d2 external-secrets: upgrade to 2.8.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:45:16 +02:00
Ruben Hensen 0bf2245c26 external-secrets: upgrade to 2.7.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:41:28 +02:00
Ruben Hensen af99a17ff4 external-secrets: upgrade to 2.6.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:38:20 +02:00
Ruben Hensen 8cc26bb412 external-secrets: upgrade to 2.5.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:34:53 +02:00
Ruben Hensen c6424cc4a5 external-secrets: upgrade to 2.4.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:31:04 +02:00
Ruben Hensen 12a1f80902 external-secrets: upgrade to 2.3.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:27:15 +02:00
Ruben Hensen 39cc61236f external-secrets: upgrade to 2.2.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:23:28 +02:00
Ruben Hensen 42fc278f74 external-secrets: upgrade to 2.1.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:19:41 +02:00
Ruben Hensen 94fc9aeb52 external-secrets: upgrade to 2.0.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:16:04 +02:00
Ruben Hensen 724afbf4f7 external-secrets: upgrade to 1.3.2
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:12:17 +02:00
Ruben Hensen cef4466925 external-secrets: upgrade to 1.2.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:08:29 +02:00
Ruben Hensen 660cb82922 external-secrets: upgrade to 1.1.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 22:02:19 +02:00
Ruben Hensen f31a31cfde external-secrets: upgrade to 1.0.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:59:01 +02:00
Ruben Hensen 4b7682f12e external-secrets: upgrade to 0.20.4
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:55:04 +02:00
Ruben Hensen 3b5708fd64 external-secrets: upgrade to 0.19.2
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:51:17 +02:00
Ruben Hensen 6cac51ebfa external-secrets: upgrade to 0.18.2
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:47:31 +02:00
Ruben Hensen c5bb001287 external-secrets: upgrade to 0.17.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:42:52 +02:00
Ruben Hensen 7acb7eaa8c Move every ExternalSecret and the ClusterSecretStore to external-secrets.io/v1
ESO 0.16.2 is the one release that serves both v1beta1 and v1. 0.17
stops serving v1beta1, so manifests still on v1beta1 would fail to sync
from the next hop on. For these resources the schemas are name-identical
(conversion strategy None); only the apiVersion changes.
2026-10-22 21:41:28 +02:00
Ruben Hensen 9e31727298 external-secrets: upgrade to 0.16.2
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:26:42 +02:00
Ruben Hensen e62728027b external-secrets: upgrade to 0.15.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:23:25 +02:00
Ruben Hensen 183686ea34 external-secrets: upgrade to 0.14.4
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:20:19 +02:00
Ruben Hensen 950d4807f2 external-secrets: upgrade to 0.13.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:16:40 +02:00
Ruben Hensen 3db1ee84a5 external-secrets: upgrade to 0.12.1
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 21:02:10 +02:00
Ruben Hensen 04e862d453 external-secrets: upgrade to 0.11.0
One minor at a time from 0.10.7 to 2.13.0, see docs/upgrade-k8s-1.33.md.
2026-10-22 20:53:13 +02:00
Ruben Hensen 096eb60f8c external-secrets: sync with server-side apply
Needed from ESO 0.19, whose CRDs are too big for client-side apply. Turned on now, on 0.10.7, so Argo CD migrates the managed fields before the upgrade starts.
2026-10-22 20:51:55 +02:00
Ruben Hensen 2a2594a987 docs: tick off CloudNativePG 1.30.1 and the Vault chart 2026-10-22 16:27:13 +02:00
Ruben Hensen b86942077a vault: recreate the injector instead of rolling it
Dropping the anti-affinity wasn't enough: during the rollout the old ReplicaSet kept recreating its pod with the old anti-affinity, which still blocked the new one. Recreate stops the old pod first; nothing uses the injector, so the short gap doesn't matter.
2026-10-22 16:22:59 +02:00
Ruben Hensen 6b81033f70 vault: drop the injector's anti-affinity
The chart requires injector pods on different nodes. With one node and one replica the rolling update to vault-k8s 1.7.6 deadlocked: the new pod stayed Pending until the old one left, which waits for the new one. The server already sets affinity to "" for the same reason.
2026-10-22 16:11:13 +02:00
Ruben Hensen e518e1368f vault: upgrade the chart to 0.34.1, keep the server on 1.17.2
Chart 0.28.1 is only tested up to Kubernetes 1.30. 0.34.1 brings the
injector to vault-k8s 1.7.6. The server image is pinned to the running
1.17.2: the StatefulSet uses OnDelete, so nothing restarts now, but a
later pod restart would otherwise pull the chart's default and Shamir
unsealing needs the keys at hand for a Vault upgrade. Rendered with the
pin, the StatefulSet only changes in formatting and an extra check in the
config script that doesn't apply here.
2026-10-22 16:06:28 +02:00
Ruben Hensen 9b9bd8bad0 cnpg: upgrade operator to 1.30.1 (chart 0.29.1)
One minor at a time from 1.25.1 to 1.30.1, see docs/upgrade-k8s-1.33.md. In-place instance manager updates keep the database pods running.
2026-10-22 15:52:41 +02:00
Ruben Hensen 7eb69b17e1 cnpg: upgrade operator to 1.29.1 (chart 0.28.3)
One minor at a time from 1.25.1 to 1.30.1, see docs/upgrade-k8s-1.33.md. In-place instance manager updates keep the database pods running.
2026-10-22 15:49:27 +02:00
Ruben Hensen b0ed6fdad1 cnpg: upgrade operator to 1.28.1 (chart 0.27.1)
One minor at a time from 1.25.1 to 1.30.1, see docs/upgrade-k8s-1.33.md. In-place instance manager updates keep the database pods running.
2026-10-22 15:46:02 +02:00
Ruben Hensen 9cf0c7f9e9 cnpg: upgrade operator to 1.27.1 (chart 0.26.1)
One minor at a time from 1.25.1 to 1.30.1, see docs/upgrade-k8s-1.33.md. In-place instance manager updates keep the database pods running.
2026-10-22 15:42:35 +02:00
Ruben Hensen 8a409c6a5b cnpg: upgrade operator to 1.26.1 (chart 0.25.0)
One minor at a time from 1.25.1 to 1.30.1, see docs/upgrade-k8s-1.33.md. In-place instance manager updates keep the database pods running.
2026-10-22 15:35:58 +02:00
Ruben Hensen 8cb8b28cd9 cnpg: prepare for the operator upgrade to 1.30
Pin authentik-postgres to the image CNPG filled in at creation
(postgresql:17.4). Later operators default to PostgreSQL 18, and since
1.26 a higher major in the image triggers an offline in-place major
upgrade. immich-postgres already pins its pgvecto.rs image.

Turn on ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES so the five operator hops
(1.25 -> 1.30, one minor at a time as the docs recommend) swap the
instance manager inside the running pods instead of restarting both
single-instance databases each time.
2026-10-22 15:35:18 +02:00
Ruben Hensen bdbabde317 docs: tick off Velero 1.16.2
Test backup of gatus and ntfy completed on the new version.
2026-10-22 15:32:57 +02:00
Ruben Hensen bd2606591e velero: correct the upgradeCRDs comment
Argo CD applies the chart's crds/ directory on every sync, so CRD updates don't depend on the hook; the 1.16 upgrade confirmed it.
2026-10-22 15:32:19 +02:00
Ruben Hensen ce1115d4f9 velero: upgrade to 1.16.2 (chart 10.1.3)
Velero 1.15 is only tested up to Kubernetes 1.31; 1.16 is tested on 1.33.
The AWS plugin moves along to v1.12.2. Argo CD applies the chart's crds/
directory itself, so the CRD schema update doesn't need the disabled
upgrade hook. No backup was running.
2026-10-22 15:30:11 +02:00
Ruben Hensen f36b90557b docs: tick off cert-manager 1.20.4
All certificates stayed Ready through the five hops, and a test Certificate for s2.rubenhensen.nl was issued by Let's Encrypt over HTTP-01. The 1.19 chart left a duplicate tokenrequest RoleBinding behind, removed by hand.
2026-10-22 15:21:28 +02:00
Ruben Hensen 629d137c1e cert-manager: upgrade to v1.20.4
One minor at a time from v1.15.5 to v1.20.4 on the way to Kubernetes 1.33, see docs/upgrade-k8s-1.33.md. The chart renders the current values unchanged.
2026-10-22 15:16:37 +02:00
Ruben Hensen 1582f67cda cert-manager: upgrade to v1.19.6
One minor at a time from v1.15.5 to v1.20.4 on the way to Kubernetes 1.33, see docs/upgrade-k8s-1.33.md. The chart renders the current values unchanged.
2026-10-22 15:12:51 +02:00
Ruben Hensen b4d7845349 cert-manager: upgrade to v1.18.6
One minor at a time from v1.15.5 to v1.20.4 on the way to Kubernetes 1.33, see docs/upgrade-k8s-1.33.md. The chart renders the current values unchanged.
2026-10-22 15:09:13 +02:00
Ruben Hensen 9d4c9c8296 cert-manager: upgrade to v1.17.4
One minor at a time from v1.15.5 to v1.20.4 on the way to Kubernetes 1.33, see docs/upgrade-k8s-1.33.md. The chart renders the current values unchanged.
2026-10-22 15:05:28 +02:00
Ruben Hensen 822270d8b3 cert-manager: upgrade to v1.16.5
One minor at a time from v1.15.5 to v1.20.4 on the way to Kubernetes 1.33, see docs/upgrade-k8s-1.33.md. The chart renders the current values unchanged.
2026-10-22 15:03:26 +02:00
Ruben Hensen ce881ac7d7 docs: tick off Longhorn 1.11.2
Longhorn is done: all volumes on engine v1.11.2, PV nodeAffinity unchanged, offline replica rebuilding still off, 17 test backups written.
2026-10-22 15:00:08 +02:00
Ruben Hensen 0514a4248a longhorn: upgrade to 1.11.2
Last hop of the Longhorn upgrade for Kubernetes 1.33. Stays on 1.11.2:
1.11.3 ships csi-provisioner v6.3.0 and needs Kubernetes 1.34. The
1.11.2 chart still declares kubeVersion >=1.25 and ships csi-provisioner
v5.3.0, and renders our values unchanged.

Checked beforehand: 17 healthy volumes plus 2 detached, no backing
images, system backup pre-upgrade-v1-10-2-202610221449 is Ready. PV
nodeAffinity recorded to compare after the upgrade (1.11.0 had a
regression there, fixed in 1.11.2).
2026-10-22 14:51:56 +02:00
Ruben Hensen d0b36b6542 docs: tick off Longhorn 1.10.2
All volumes on engine v1.10.2 with 19 replicas, backup target fine, 17 test backups written.
2026-10-22 14:40:22 +02:00
Ruben Hensen 7bb7813d1d longhorn: upgrade to 1.10.2
Third hop towards 1.11.2. 1.10 removes the longhorn.io/v1beta1 API, which
requires every Longhorn CRD to store only v1beta2; all 22 already do (the
check from the 1.10 important notes). Settings move to a per-data-engine
JSON format, but the chart renders our defaultSettings and
defaultBackupStore values unchanged.

Checked beforehand: 17 healthy volumes plus 2 detached, no backing
images, system backup pre-upgrade-v1-9-2-202610221421 is Ready.
2026-10-22 14:23:18 +02:00
Ruben Hensen 53f01c65dc docs: tick off Longhorn 1.9.2
All volumes on engine v1.9.2, backup target fine, 17 test backups written. Every Longhorn CRD already stores only v1beta2.
2026-10-22 14:19:28 +02:00
Ruben Hensen a73bdb8fb4 longhorn: upgrade to 1.9.2
Second hop towards 1.11.2. 1.9 stops serving longhorn.io/v1beta1 (nothing
in this repo uses it) and renames orphan-auto-deletion (false here) to
orphan-resource-auto-deletion during the upgrade. Chart values are
unchanged from 1.8.2.

Checked beforehand: 17 healthy volumes plus 2 detached, no backing
images, every Longhorn CRD already stores only v1beta2, and system backup
pre-upgrade-v1-8-2-202610221408 is Ready.
2026-10-22 14:11:09 +02:00
Ruben Hensen f390b3a70d docs: tick off Longhorn 1.8.2
All 19 volumes on engine v1.8.2, BackupTarget default points at the NAS, and a manual run of backup-daily wrote 17 backups.
2026-10-22 14:01:30 +02:00
Ruben Hensen fae03f3b8b longhorn: upgrade to 1.8.2
First hop from 1.7.3 to 1.11.2 (docs/upgrade-k8s-1.33.md). 1.8 drops the
backup-target settings in favour of a "default" BackupTarget resource, so
the NFS target and poll interval move into defaultBackupStore. Until now
they only lived in the cluster.

Checked beforehand: no Faulted volumes, no backing images, all volumes on
engine v1.7.3, system backup pre-upgrade-v1-7-3-20261022 and Velero
backup pre-longhorn-1-8-202610221326 both complete.
2026-10-22 13:52:13 +02:00
Ruben Hensen f2c1b9ac06 docs: fix the Longhorn important-notes links
Docs for older Longhorn versions live under /docs/archives/.
2026-10-22 13:27:28 +02:00
Ruben Hensen 119f7729f6 docs: tick off upgrade step 1
All Longhorn volumes run engine v1.7.3, the 1.7.1 and 1.7.2 engine images are gone, and system backup pre-upgrade-v1-7-3-20261022 is Ready.
2026-10-22 12:58:59 +02:00
Ruben Hensen 6da1b3e88e longhorn: upgrade volume engines automatically, one at a time
concurrentAutomaticEngineUpgradePerNodeLimit was 0, so volumes stayed on
the engine image of whatever Longhorn version created them: three on
1.7.1, nine on 1.7.2, seven on 1.7.3. Every hop of the upgrade to 1.11.2
needs all volumes on the current engine first.
2026-10-22 12:56:21 +02:00
Ruben Hensen 8aaf2ec8ec Plan the move to Kubernetes 1.33
Envoy Gateway v1.9 needs Kubernetes 1.33, and microk8s 1.32 is out of
upstream support. docs/upgrade-k8s-1.33.md lists what has to move first
and in which order. Renovate is held below Longhorn 1.11.3, since that
and newer releases need Kubernetes 1.34.
2026-10-22 12:56:07 +02:00
Ruben Hensen f2716e1169 home-assistant: mark the EndpointSlice endpoint ready
The API server fills in conditions on every endpoint, which left Argo CD showing the slice as OutOfSync. Spell it out so desired and live state match.
2026-10-22 11:07:42 +02:00