Compare commits

..
Author SHA1 Message Date
Ruben Hensen 6c727346f6 renovate: patch updates of low-risk apps merge themselves 2026-10-26 23:23:25 +01:00
Ruben Hensen 0dc69d34f0 Merge pull request #50 from rubenhensen/proxy-protocol
Pass the visitor's address from node001 to the home cluster
2026-10-26 23:12:14 +01:00
Ruben Hensen 30540ea579 node001: send the visitor's address to the home cluster
The stream server on 443 now starts each connection with a PROXY header.
nginx sends it to every upstream or none, so Stalwart (8443) and the
local nginx for Gatus and ntfy (8444) get theirs through a hop on
8445/8446 that takes it off again; nothing changes for them.

Deploy after the Gateway accepts the header, or the tunneled hosts stop
answering until it does.
2026-10-26 23:11:38 +01:00
Ruben Hensen 53d74768ad gateway: take the visitor's address from a PROXY header
node001 passes TLS through without opening it, so every request from
the tunneled hosts arrives from 46.224.26.65. Wordfence locked that
address out after 20 failed logins on 2026-10-26, and with it everyone
who logs in to scoutingmbg.nl. With a PROXY header from node001, Envoy
puts the visitor's address in X-Forwarded-For instead.

The header is optional: s2 and ntfy2 point straight at home, and
node001's proxy on port 80 sends none either.
2026-10-26 23:11:38 +01:00
Ruben Hensen b6462fb3a9 Merge pull request #49 from rubenhensen/roadmap-garage
docs: Velero on Garage
2026-10-26 23:04:15 +01:00
Ruben Hensen bed68c70a8 velero: the switch to Garage was on 10-26 2026-10-26 22:57:35 +01:00
Ruben Hensen 3991a8d726 docs: Velero on Garage, and the off-site copy from the bucket 2026-10-26 22:57:35 +01:00
Ruben Hensen 648f99c505 Merge pull request #35 from rubenhensen/velero-garage
Velero backs up to Garage instead of MinIO
2026-10-26 22:52:42 +01:00
Ruben Hensen 20bd3a4bca Merge pull request #39 from rubenhensen/immich-ml-v2
immich: the optimized ML models, cached on a volume
2026-10-25 17:48:40 +01:00
Ruben Hensen 6cba1a9363 immich: the optimized ML models, cached on a volume 2026-10-25 17:46:03 +01:00
Ruben Hensen acfce6645e velero: skip PVCs in Longhorn's no-backup group 2026-10-25 17:46:03 +01:00
Ruben Hensen 0de86dd65c Merge pull request #36 from rubenhensen/renovate-re2
Renovate: skip the non-app folders without a lookahead
2026-10-25 17:41:32 +01:00
Ruben Hensen d7ffdc05f6 docs: Renovate rejected the lookahead (#32) 2026-10-25 17:33:39 +01:00
Ruben Hensen c0f8034e14 renovate: skip the non-app folders through ignorePaths, not a lookahead 2026-10-25 17:33:39 +01:00
Ruben Hensen a15a4f7c75 Merge pull request #34 from rubenhensen/velero-garage-secret
Garage on the NAS, and Velero's key for it
2026-10-25 17:23:33 +01:00
Ruben Hensen bdafcaf1e0 backup-testing: read Velero's key for Garage 2026-10-25 17:10:32 +01:00
Ruben Hensen 03c3196242 velero: back up to Garage instead of MinIO 2026-10-25 17:10:32 +01:00
Ruben Hensen b072099cc1 nas: Garage keeps its metadata in SQLite 2026-10-25 17:08:13 +01:00
Ruben Hensen e10ca337f1 velero: a key for Garage, from Vault 2026-10-25 16:28:43 +01:00
Ruben Hensen c72b08867f nas: Garage, which takes over from MinIO 2026-10-25 16:28:43 +01:00
Ruben Hensen d85362ce3b docs: the restore test passed against the real backups 2026-10-25 14:57:18 +01:00
Ruben Hensen 018f528fb3 docs: a WordPress cache without plugins 2026-10-25 14:56:10 +01:00
Ruben Hensen 714712b862 docs: WordPress is capped at 12 workers 2026-10-25 13:11:20 +01:00
Ruben Hensen 7dc13466cb mbgwp: cap Apache at 12 workers so a crawler can't run it out of memory 2026-10-25 13:07:30 +01:00
Ruben Hensen 9b77596bcb backup-testing: take endpoint, region and bucket from Velero's location 2026-10-25 12:59:25 +01:00
Ruben Hensen fbf2cb2d92 docs: the unseal key is kept safe 2026-10-25 12:57:18 +01:00
Ruben Hensen 122873ca5c docs: hensen.io can expire 2026-10-25 12:54:32 +01:00
Ruben Hensen 71449dd185 docs: record the external-secrets upgrade 2026-10-25 12:54:01 +01:00
Ruben Hensen 297d2dffa5 Merge pull request #17 from rubenhensen/renovate/external-secrets-2.x
chore(deps): update helm chart external-secrets to v2.14.0
2026-10-25 12:50:28 +01:00
Ruben Hensen 46117ee658 chore(deps): update helm chart external-secrets to v2.14.0 2026-10-25 12:49:06 +01:00
Ruben Hensen 2a5bbc7f44 docs: the scoutingmbg.nl DNS questions are answered
Only the four records moved to node001, hensen.io is no longer needed, and SPF's a mechanism doesn't matter since all mail goes through Google.
2026-10-25 12:39:57 +01:00
Ruben Hensen d7b0372f1a docs: record the rest of the merged PRs 2026-10-25 12:37:25 +01:00
Ruben Hensen 0ad6ca816c docs: who cleaned up the snapshots, and the stalls per minute
Every minute with dqlite errors in the 23 hours sampled had the SSD fully busy; the controllers with 60s leases held.
2026-10-25 12:35:47 +01:00
Ruben Hensen 3e252799a4 Merge pull request #26 from rubenhensen/renovate/gitea-gitea-28.x
chore(deps): update gitea/gitea docker tag to v28
2026-10-25 12:25:03 +01:00
Ruben Hensen bfd5619e9e Merge pull request #27 from rubenhensen/renovate/github.com-canonical-go-dqlite-v3-3.x
fix(deps): update module github.com/canonical/go-dqlite/v3 to v3.0.4
2026-10-25 12:24:30 +01:00
Ruben Hensen 0b38d8dec8 Merge pull request #33 from rubenhensen/requests
Set resource requests from measured usage
2026-10-25 12:23:54 +01:00
Ruben Hensen 083353fb9d Merge pull request #23 from rubenhensen/renovate/binwiederhier-ntfy-2.x
chore(deps): update binwiederhier/ntfy docker tag to v2.34.0
2026-10-25 12:22:45 +01:00
Ruben Hensen 23f9c5c60a docs: record the merged Renovate PRs 2026-10-25 12:21:38 +01:00
Ruben Hensen a8bf3d5b64 Merge pull request #31 from rubenhensen/renovate/python-3.x
chore(deps): update python docker tag to v3.15.1
2026-10-25 12:17:31 +01:00
Ruben Hensen 618954ae2c Merge pull request #25 from rubenhensen/renovate/wordpress-0.x
chore(deps): update helm chart wordpress to v0.16.7
2026-10-25 12:17:17 +01:00
Ruben Hensen 44dc85d306 Merge pull request #24 from rubenhensen/renovate/https-github.com-kubernetes-csi-external-snapshotter.git-8.x
chore(deps): update dependency https://github.com/kubernetes-csi/external-snapshotter.git to v8.7.0
2026-10-25 12:16:25 +01:00
Ruben Hensen b60735f6b0 Merge pull request #28 from rubenhensen/renovate/cert-manager-1.21.x
chore(deps): update helm chart cert-manager to v1.21.3
2026-10-25 12:14:55 +01:00
Ruben Hensen 3a57e5be48 docs: WordPress went out of memory under a crawler 2026-10-25 09:45:33 +01:00
Ruben Hensen 1611f5d1ef docs: PR 33's window and Renovate's PR limit 2026-10-25 09:44:20 +01:00
Ruben Hensen 5bb1422594 Raise two requests after the morning's numbers 2026-10-25 09:43:11 +01:00
Ruben Hensen 68b692a112 docs: requests are in PR 33 2026-10-25 07:10:37 +01:00
Ruben Hensen 72f49bed51 Set resource requests from measured usage 2026-10-25 07:08:16 +01:00
Ruben Hensen f4b42757cd backup-testing: remove k3s's anonymous volumes too 2026-10-25 07:04:17 +01:00
Ruben Hensen f529bd99ee docs: triage PR 31 2026-10-25 07:02:07 +01:00
Ruben Hensen 74dec430b8 docs: the restore test is ready to run 2026-10-25 07:01:04 +01:00
Ruben Hensen 6fe0acc061 backup-testing: a restore test from a read-only copy of the bucket 2026-10-25 07:00:49 +01:00
Ruben Hensen bb34b601d9 docs: the system backups' snapshots hold 258 GiB 2026-10-25 04:35:58 +01:00
Ruben Hensen e98668d5fa docs: the cluster check has six parts 2026-10-25 04:35:02 +01:00
Ruben Hensen 389f911823 gatus: also report unhealthy Argo CD apps and CNPG clusters 2026-10-25 04:34:32 +01:00
Ruben Hensen 8f1c6a5b6e docs: record the repo rules 2026-10-25 04:33:01 +01:00
Ruben Hensen 770631fdc0 ci: check the repo's own manifests for secrets in git and unpinned images 2026-10-25 04:32:13 +01:00
Ruben Hensen 855317b84d freshrss: pin the alpine/git init container 2026-10-25 04:32:13 +01:00
Ruben Hensen d69f2638d1 docs: record the vulnerability scan and the old Longhorn instance manager 2026-10-25 04:29:57 +01:00
Ruben Hensen 90e552c9f5 docs: update the roadmap's state 2026-10-25 04:25:43 +01:00
Ruben Hensen ad14995ba0 docs: record the wider Renovate coverage 2026-10-25 04:25:10 +01:00
Ruben Hensen c359384ade renovate: look at every app folder, and at CNPG images 2026-10-25 04:24:56 +01:00
Ruben Hensen a4fc386ee8 docs: record the new probes 2026-10-25 04:22:28 +01:00
Ruben Hensen 0dc0bc4322 docs: authentik's base URL is already set 2026-10-25 04:22:06 +01:00
Ruben Hensen d843f31d86 serpbear: add health probes 2026-10-25 04:19:29 +01:00
Ruben Hensen da23357946 freshrss: add health probes 2026-10-25 04:19:29 +01:00
Ruben Hensen b9d88f41b9 gitea: add health probes 2026-10-25 04:19:29 +01:00
Ruben Hensen 3c4a8cc8db docs: bring the authentik README up to date 2026-10-25 04:16:48 +01:00
Ruben Hensen d17e78130d docs: record metrics-server and plan the restore test 2026-10-25 04:15:43 +01:00
Ruben Hensen 22c5a325d6 Add metrics-server 2026-10-25 04:11:59 +01:00
renovate[bot] 6b2f5855d7 chore(deps): update python docker tag to v3.15.1 2026-10-25 03:10:52 +00:00
Ruben Hensen ef07307f93 renovate: keep CI's Helm at Argo CD's version 2026-10-25 04:10:30 +01:00
Ruben Hensen aa940134ea docs: record the CI and the Renovate triage 2026-10-25 04:10:14 +01:00
Ruben Hensen f86ed09cd8 renovate: drop the github-tags manager, which duplicated the argocd one 2026-10-25 04:09:52 +01:00
Ruben Hensen 6d2bc379ba ci: retry when a registry rate-limits 2026-10-25 04:06:53 +01:00
renovate[bot] c25b8883da chore(deps): update gitea/gitea docker tag to v28 2026-10-25 03:06:44 +00:00
renovate[bot] 18f9e2efe6 chore(deps): update helm chart wordpress to v0.16.7 2026-10-25 03:06:35 +00:00
renovate[bot] 5f5f5b01f0 chore(deps): update dependency https://github.com/kubernetes-csi/external-snapshotter.git to v8.7.0 2026-10-25 03:06:27 +00:00
renovate[bot] 6206ab5a74 chore(deps): update binwiederhier/ntfy docker tag to v2.34.0 2026-10-25 03:06:23 +00:00
renovate[bot] 075b3686c3 chore(deps): update helm chart cert-manager to v1.21.3 2026-10-25 03:05:55 +00:00
Ruben Hensen 67c21c30d8 Render and validate every app on PRs and pushes 2026-10-25 03:57:24 +01:00
Ruben Hensen 0c52d8a467 apps: list external-snapshotter's automated sync once 2026-10-25 03:57:24 +01:00
Ruben Hensen f2e4c5aff6 docs: record the backup check 2026-10-25 03:49:43 +01:00
Ruben Hensen d836e4608c gatus: check backups and Vault's seal from inside the cluster 2026-10-25 03:48:05 +01:00
Ruben Hensen 1f56e67e8b docs: what the disk did in the last day, and foto's DNS 2026-10-25 03:42:13 +01:00
Ruben Hensen cadac4cebf docs: record the cleanup and what is left of it 2026-10-25 03:29:55 +01:00
Ruben Hensen bc71061db7 Remove commented-out files, the empty secrets app and a stale script copy 2026-10-25 03:27:32 +01:00
Ruben Hensen 7d3a64e5c8 docs: record the NetworkPolicies for the other apps and Vault 2026-10-25 03:24:07 +01:00
Ruben Hensen e137e79b75 vault: only ESO, Envoy and the node reach Vault 2026-10-25 03:21:53 +01:00
Ruben Hensen 67dc4f0783 Limit the other public apps to their own pods, DNS and the internet 2026-10-25 03:21:53 +01:00
Ruben Hensen 684f536f2f docs: record the NetworkPolicies for immich, mbgwp and authentik 2026-10-25 03:17:11 +01:00
Ruben Hensen 1439466af4 authentik: limit the pods to each other, DNS and the internet 2026-10-25 03:15:20 +01:00
Ruben Hensen 57514c3c14 immich: limit the pods to each other, DNS and the internet 2026-10-25 03:12:02 +01:00
Ruben Hensen 57851bf43a mbgwp: limit WordPress to its database, DNS and the internet 2026-10-25 03:09:06 +01:00
Ruben Hensen ada909ee02 docs: plan off-site backups through a friend's bucket 2026-10-25 03:05:39 +01:00
Ruben Hensen 345de16552 docs: record the Vault 2.2.1 upgrade 2026-10-25 02:52:52 +01:00
Ruben Hensen 7396cc3ed6 vault: fix the listing-visibility flag in the OIDC job 2026-10-25 02:52:02 +01:00
Ruben Hensen 26ca83457c vault: upgrade to 2.2.1, with a script to roll the pods 2026-10-25 02:40:45 +01:00
Ruben Hensen 4709194483 docs: tick off the authentik login test 2026-10-25 02:40:45 +01:00
Ruben Hensen ad2d6fbae5 docs: record the authentik 2026.8 upgrade 2026-10-25 02:34:51 +01:00
Ruben Hensen 077711472e authentik: upgrade to 2026.8.5 2026-10-25 02:31:00 +01:00
Ruben Hensen 43f741141d authentik: upgrade to 2026.5.6 2026-10-25 02:23:15 +01:00
Ruben Hensen cbee4955d3 authentik: drop the redis values, which the chart no longer has 2026-10-25 02:23:15 +01:00
Ruben Hensen a70dff6fdd docs: add a roadmap in place of the wishlist 2026-10-25 02:16:31 +01:00
Ruben Hensen ab0a09a356 docs: the immich login moved to auth.scoutingmbg.nl 2026-10-25 02:08:59 +01:00
Ruben Hensen b2649a682c immich: log in through auth.scoutingmbg.nl
The Scouts Online connection now redirects to auth.scoutingmbg.nl, the
group's own domain for the authentik login, so immich's OAuth issuer
moves there too.
2026-10-25 02:03:50 +01:00
Ruben Hensen ce3846bcd3 node001: tunnel scoutingmbg.nl and www to the home cluster
The group's DNS moved scoutingmbg.nl (A to node001) and www (CNAME to
rubenhensen.nl) here as well, so the WordPress site got node001's mail
certificate. Pass them through to the home cluster like foto and auth.
2026-10-25 02:59:00 +02:00
Ruben Hensen 96c13c63f7 authentik: serve auth.scoutingmbg.nl
A Gateway listener with its own certificate, the authentik route on both
hostnames, and an authentik brand for auth.scoutingmbg.nl that logs in
through Scouts Online and then sends people to the photos. The
authentik.rubenhensen.nl brand stays as it is.
2026-10-24 18:52:24 +02:00
Ruben Hensen 70151b0ef4 authentik: certificate for auth.scoutingmbg.nl
The login of the Scouting MBG photos moves to the group's own domain; the Gateway listener follows once the certificate is there.
2026-10-24 18:51:27 +02:00
Ruben Hensen f5e8b1e633 node001: tunnel auth.scoutingmbg.nl to the home cluster
The group's DNS points auth.scoutingmbg.nl at rubenhensen.nl too; it will carry the authentik login for immich.
2026-10-24 17:58:34 +02:00
Ruben Hensen ae2e5ad9fa docs: record the foto.scoutingmbg.nl DNS change 2026-10-24 17:48:35 +02:00
Ruben Hensen 8cf87483d6 node001: tunnel foto.scoutingmbg.nl to the home cluster
The group's DNS now points foto.scoutingmbg.nl at rubenhensen.nl, which is
this server, instead of mbg.hensen.io (the home IP). Resolvers that had
picked up the change got node001's own certificate and no immich. Add the
host to the SNI passthrough and the port 80 proxy like the other tunneled
hosts, so it works through either record.
2026-10-24 17:47:14 +02:00
Ruben Hensen c5d2ebaefc docs: record the Envoy retry policy 2026-10-24 17:06:29 +02:00
Ruben Hensen 5f8394e0c0 docs: plan a second SSD for Longhorn
Hardware to buy, shrinking the data first (214 GiB of old snapshots), installing the NVMe drive, and moving every replica over with a disk eviction.
2026-10-24 15:17:15 +02:00
Ruben Hensen 396eb2665c docs: record why controllers still lost their leases
Heavy writes on the node's only SSD stall dqlite; the fixes so far, the running measurement and the second-SSD option.
2026-10-24 14:46:09 +02:00
Ruben Hensen 858904384c Give leader-elected controllers longer leases
The snapshot-controller (1,059 restarts), the CNPG operator and Envoy
Gateway restart whenever a lease renewal takes more than 10 seconds,
which happens when heavy writes stall dqlite on the node's SSD. Raise
lease duration, renew deadline and retry period from 15s/10s/2s to
60s/40s/5s so they ride out stalls of up to ~40 seconds. With one
replica, or a standby, a slower takeover costs nothing here.
2026-10-24 14:43:38 +02:00
Ruben Hensen 9014898fc5 velero: run kopia maintenance daily and throttled
Each of the 15 kopia repositories ran maintenance every hour, and about
once a day a full run of several minutes that writes its cache to the
node's only SSD. Those runs line up with dqlite stalling for seconds and
controllers losing their leases (vault 09:57-10:07, argocd and mbgwp
09:17-09:40 today). Make the default frequency 24h and cap the jobs at
half a CPU, so a full run writes slower and longer instead of in one
burst.
2026-10-24 14:43:38 +02:00
Ruben Hensen 111a9ddcea docs: foto@ is deleted 2026-10-24 14:20:07 +02:00
Ruben Hensen a8296a514e docs: foto@'s likes are deleted 2026-10-24 14:19:00 +02:00
Ruben Hensen 712fa1fe65 docs: sol-auth is gone 2026-10-24 14:15:14 +02:00
Ruben Hensen c3505bc8e3 immich: remove sol-auth
foto.scoutingmbg.nl goes straight to immich since the switch to Scouts
Online, so the Apache with mod_auth_openid (OpenID 2) in front of it has
no traffic left.
2026-10-24 14:14:43 +02:00
Ruben Hensen 6c6f473f63 docs: fotoupload@ sessions ended 2026-10-24 14:13:40 +02:00
Ruben Hensen a5478d60e6 docs: share-sync joins albums that kaderleden create 2026-10-24 14:11:07 +02:00
Ruben Hensen 88f68cd698 immich: share albums that kaderleden create automatically
Nobody uses the group account anymore, so new albums belong to the
leiding who make them, and share-sync only shared albums the group
account was in. It now first adds the group account as editor to every
album an uploader owns (straight in the database: the API only lets an
album's owner or editors share it), after which the album goes to
everyone like the others. Albums whose name starts with "Privé" or
"Prive" are left alone.
2026-10-24 14:10:30 +02:00
Ruben Hensen f69b790a58 docs: immich now logs in with Scouts Online only 2026-10-24 14:04:43 +02:00
Ruben Hensen 71af3a9342 immich: fix hiding album invitations in share-sync
immich stores a notification's data as a JSON string inside the jsonb column, so data->>'albumId' was always null and no invitation was hidden. Unwrap it first.
2026-10-24 14:03:02 +02:00
Ruben Hensen 348cce6d5d gatus: check immich's ping endpoint for foto.scoutingmbg.nl
Without sol-auth in front, /_app is no longer the open path to check;
/api/server/ping answers without a login.
2026-10-24 14:01:23 +02:00
Ruben Hensen abed11dbaa immich: log in with Scouts Online only
foto.scoutingmbg.nl now goes straight to immich instead of through
sol-auth. immich starts the Scouts Online login right away, the password
login is off and the login page no longer shows the password of the
shared viewing account. share-sync is on, so everyone gets every album
and the group's library in their timeline.

sol-auth stays deployed for now, so switching the route back is the way
back.
2026-10-24 14:01:23 +02:00
Ruben Hensen 86a0c59c6b immich: add share-sync, suspended
immich has no user groups, so a CronJob shares the group account's
albums with every user, as editor when they may upload (quota other than
0, which authentik sets from Scouts Online) and as viewer otherwise. It
also shares the group account's library as a partner and shows it in
every timeline, since immich only searches your own and your timeline
partners' photos; hides the album invitations for albums older than a
week; and ends OAuth sessions older than 30 days, so people who left the
group lose access at their next login.

Suspended until immich logs in through Scouts Online only.
2026-10-24 13:48:07 +02:00
Ruben Hensen ebf28c1bf1 docs: step B of the Scouts Online login is live 2026-10-24 13:43:24 +02:00
Ruben Hensen 135bca4a83 authentik: log in to immich with Scouts Online
Adds Scouts Online 3 (login.scouting.nl) as an OIDC source. Its userinfo
has the member's roles within the group; a property mapping puts every
member in "MBG leden" and those with an active Kaderlid role also in
"MBG kader", on every login. Members become external users. Family
members can share an email address and immich needs a unique one, so
those get a plus address with their member number.

The immich provider now authenticates through a flow whose only stage
is an identification stage with this one source and no fields, which
sends people straight on to Scouts Online. The source's own flows only
run through the source.
2026-10-24 13:37:12 +02:00
Ruben Hensen 1c6b42b20b docs: step A of the Scouts Online login is live 2026-10-24 13:25:02 +02:00
Ruben Hensen f3f36c3718 docs: plan the immich login with Scouts Online
Building blocks, design and the three steps towards personal accounts with upload rights from Scouts Online roles.
2026-10-24 13:19:52 +02:00
Ruben Hensen 399387bfb7 immich: configure through a config file with OAuth
immich gets its settings from a Secret that ESO renders with the OAuth
client secret from Vault. It keeps the settings that were in the database
(external domain, login page message, storage template) and adds OAuth
through authentik next to the password login, with auto register. With a
config file the settings are read-only in the admin UI.
2026-10-24 13:19:52 +02:00
Ruben Hensen 48b0873ca3 authentik: add an OIDC provider for immich
The Scouting MBG photos (immich) will log in through this authentik,
which later passes on Scouts Online. The provider issues immich_role and
immich_quota: admins and the members of "MBG kader" may upload (-1),
everyone else gets a quota of 0, which makes immich refuse uploads.
"MBG leden" and "MBG kader" are filled by the Scouts Online source in a
next step; until then only authentik Admins can use the app.

The scouting blueprints and their secrets are mounted as directories
rather than with subPath, and the blueprint reads the client secret with
!File instead of !Env, so later changes reach authentik without a restart.
2026-10-24 13:19:52 +02:00
Ruben Hensen 278f6fc55f authentik: limit personal apps to authentik Admins
Actual Budget, Argo CD, FreshRSS, Stalwart and Vault had no policy
binding, so any authentik user could sign in to them. Scouts Online
members are about to get accounts in this authentik for immich; bind
each app to the authentik Admins group, as Longhorn already was.
2026-10-24 13:04:33 +02:00
Ruben Hensen f4e74a9503 docs: record the immich 3 upgrade
v3.3.5 with chart 0.13.4 is running; note the safety net to clean up later and the optional revised ML models.
2026-10-24 12:33:43 +02:00
Ruben Hensen c270bcc12b immich: upgrade to v3.3.5 and chart 0.13.4
immich 3 drops pgvecto.rs, which the database no longer uses since the
move to PostgreSQL 17 with VectorChord 1.1.1 (supported range >=0.3 <2)
and pgvector 0.8.6 (>=0.7 <0.9). None of the removed environment
variables are set here. The mobile app cannot pass sol-auth, so there are
no app clients to upgrade first.

Charts after 0.12.0 are only published to the OCI registry. Since 0.13.0
the chart validates its values, and emptyDir volumes no longer accept
size, accessMode or storageClass; they did nothing anyway. Valkey follows
the chart's new default, 9.1.2. Each component now gets its own
ServiceAccount without a mounted token.

Safety net: Longhorn snapshot immich-pg17-pre-v3 and a pg_dump in
~/immich-pg17-pre-v3.dump on opti1, since immich cannot be downgraded.
2026-10-24 12:29:35 +02:00
Ruben Hensen 14e61ee5ee gateway: retry requests on dropped backend connections
When a backend closes a kept-alive connection just as Envoy sends a
request over it, Envoy returns a 503 (response flag UC) and does not
retry by default. ingress-nginx retried these, so the race never showed.

The Apache in front of immich (sol-auth) recycles its processes after 30
connections, which made this happen during page loads: three chunks got
a 503 and immich failed with "error loading dynamically imported module".
authentik and ntfy saw it too, less often.

Retry up to twice on connection failures and resets, for every route on
the Gateway.
2026-10-24 12:19:37 +02:00
Ruben Hensen e7696107c0 docs: record the immich database migration
immich now runs v2.7.5 on PostgreSQL 17 with VectorChord. The PostgreSQL 14 cluster stays for a few days as a fallback.
2026-10-24 02:19:57 +02:00
Ruben Hensen a8a186b4d3 immich: upgrade to v2.7.5
v2.4.1 only accepts VectorChord >=0.3 <0.6 and refused to start on the new PostgreSQL 17 cluster with VectorChord 1.1.1; from v2.5.0 the range is >=0.3 <2. v2.7.5 is the last 2.x release; the 3.x upgrade comes separately.
2026-10-24 02:12:53 +02:00
Ruben Hensen 8596e8a428 immich: use the PostgreSQL 17 cluster and start the server again
The import into immich-postgres-17 matched the old database table for table (assets, embeddings, faces, people, albums, migrations). On start immich builds its VectorChord indexes.
2026-10-24 02:06:41 +02:00
Ruben Hensen 251f22c46f immich: add a PostgreSQL 17 cluster with VectorChord
Imported once from the PostgreSQL 14 cluster, whose embeddings were converted to real[] and whose pgvecto.rs extension was dropped first (immich's manual migration). After the import the columns become vector(512) again under VectorChord 1.1.1 with pgvector 0.8.6. A logical import because CNPG can't upgrade in place from the bullseye-based pgvecto.rs image to the bookworm-based VectorChord one.
2026-10-24 02:02:02 +02:00
Ruben Hensen 60ff978b1b immich: stop the server for the database migration
The database moves from PostgreSQL 14 with pgvecto.rs to a new PostgreSQL 17 cluster with VectorChord. Immich 3 no longer supports pgvecto.rs, and PostgreSQL 14 reaches end of life on 2026-11-12.
2026-10-24 00:18:28 +02:00
Ruben Hensen 6517c21937 mbgwp: remove the unused wordpress-external NodePort
It selected pods of the old mbgwp-helm release, so since the move to the official chart it had no endpoints and only held node port 30989 open.
2026-10-24 00:08:19 +02:00
Ruben Hensen 8357d31f9c docs: record the Longhorn NetworkPolicies and poll interval 2026-10-24 00:05:44 +02:00
Ruben Hensen 5208379310 longhorn: enable the internal NetworkPolicies
With them only Longhorn's own components can reach the longhorn-manager API, which any pod could otherwise call without authentication to manage volumes. 1.12 was kept off because its instance-manager policy left the host-side iSCSI initiator out; 1.13 opens port 3260 to any source while v1DataEngineInitiatorSourceCIDRs is empty.
2026-10-24 00:02:32 +02:00
Ruben Hensen f2936e69ec docs: record the switch to annotation tracking 2026-10-24 00:01:16 +02:00
Ruben Hensen 7c8cd28f71 argocd: track resources by annotation
Drops the label tracking pin kept through the 3.x upgrades, so Argo CD uses its default argocd.argoproj.io/tracking-id annotation. Labels can be copied by other tools (cert-manager's ingress-shim copied app.kubernetes.io/instance onto Certificates); the annotation names the exact resource. Every app gets synced once right after, so resources removed later are still recognised for pruning.
2026-10-23 23:54:06 +02:00
Ruben Hensen f901beea4c docs: record the ESO storedVersions cleanup 2026-10-23 23:53:16 +02:00
Ruben Hensen 04a2a2aed2 gatus: let Argo CD prune old resources
configMapGenerator gives every config change a new gatus-config-<hash> ConfigMap, and without prune the old one stayed behind and left the app OutOfSync.
2026-10-23 23:42:58 +02:00
Ruben Hensen 947a705016 longhorn: poll the backup store every 30 minutes
Each poll updates the backupvolume objects, which made up about 8% of the k8s-dqlite writes at the 300s interval. The recurring backup runs once a night, so 30 minutes is plenty.
2026-10-23 23:39:49 +02:00
Ruben Hensen 416356b4d5 Remove the disabled apps and a stray Argo CD patch copy
Nothing deploys disable/: the apps in it (ente-photos, minio, mist, owntracks, traccar, ttrss, whisper and others) are gone from the cluster apart from some old TLS secrets. git history keeps them. The argocd-cm patch copy was an old leftover that kustomize never used.
2026-10-23 23:39:49 +02:00
Ruben Hensen d747530f52 docs: tick off the 1.36 component recheck 2026-10-23 23:37:17 +02:00
Ruben Hensen f0519d1b70 docs: record the CVE-2026-2270 patch
microk8s now runs 1.36/edge (v1.36.5) and stays held; it goes back to 1.36/stable once that channel catches up.
2026-10-23 23:35:32 +02:00
Ruben Hensen acc3d7eabb docs: tick off microk8s 1.36
v1.36.2 with containerd 2.2.3, and the snap is held. The CVE-2026-2270 patch release is still to come to the stable channel.
2026-10-23 23:24:06 +02:00
Ruben Hensen 96870af92f docs: prepare microk8s 1.36
Nothing changes in microk8s between 1.35 and 1.36 for this setup. The stable channels lag upstream patches, including the CVE-2026-2270 fix, so the snap gets held and patch updates become a deliberate step.
2026-10-23 23:18:51 +02:00
Ruben Hensen a0fcf9ec3f docs: tick off Longhorn 1.13 2026-10-23 23:15:04 +02:00
Ruben Hensen b19c776728 longhorn: upgrade to 1.13.0
1.13 needs Kubernetes 1.34 or later. It adds a longhorn-global-manager Deployment, set to one replica on this single node, and by default lets the CSI controller read every Secret for provisioner-secret StorageClass parameters; neither StorageClass uses those, so that grant stays off.
2026-10-23 23:06:08 +02:00
Ruben Hensen 514fcd8dd4 longhorn: upgrade to 1.12.1
First step from 1.11.2 to 1.13 now that the cluster runs Kubernetes 1.35. The internal NetworkPolicies that 1.12 enables by default stay off: Calico would enforce them, and the instance-manager policy only admits Longhorn pods while the iSCSI initiator connects from the host.

Also lifts the Renovate hold below 1.11.3, which only existed for Kubernetes 1.33.
2026-10-23 22:58:29 +02:00
Ruben Hensen bd8643c00b docs: tick off Velero 1.18 2026-10-23 22:48:57 +02:00
Ruben Hensen 1926ccc42a velero: upgrade to 1.18.2 (chart 12.2.1)
No breaking changes for this setup: the chart renders the same resources and server flags, and chart 12 only dropped the Bitnami kubectl image from the CRD hook, which stays off because Argo CD applies the CRDs. The AWS plugin goes to v1.14.4, the line for Velero 1.18.
2026-10-23 22:47:27 +02:00
Ruben Hensen e3074b43ad velero: upgrade to 1.17.1 (chart 11.4.0)
1.17 drops restic, which nothing here uses (all 411 pod volume backups and 20 repositories are kopia), and moves the maintenance job settings from server flags into the velero-repo-maintenance ConfigMap, which the chart now renders with keepLatestMaintenanceJobs: 3. The AWS plugin goes to v1.13.2, the line for Velero 1.17.
2026-10-23 22:45:00 +02:00
Ruben Hensen 04ac64f956 docs: tick off Argo CD 3.5 2026-10-23 22:42:00 +02:00
Ruben Hensen e490c79e78 argocd: upgrade to v3.5.6
3.5 is tested on Kubernetes 1.32 to 1.36; 3.4 stops at 1.35. It renders Helm charts with Helm 4.2.1 instead of 3.19; rendering all thirteen Helm apps with both gave the same manifests apart from whitespace, comments and document order.
2026-10-23 22:35:00 +02:00
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
renovate[bot] 45d1ea0d93 fix(deps): update module github.com/canonical/go-dqlite/v3 to v3.0.4 2026-10-23 20:04:51 +00: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
Ruben Hensen a10dbecc94 home-assistant: replace the ExternalName service with an EndpointSlice
After the microk8s ingress addon went from ingress-nginx 1.8.0 to 1.13.8,
ha.rubenhensen.nl returned 503: the controller now resolves externalName
as a DNS name and "192.168.1.202" fails the lookup. A selector-less
Service with an EndpointSlice pointing at the IP is the supported way to
route to an address outside the cluster.
2026-10-22 11:03:19 +02:00
Ruben Hensen 2ce9c33dbd Remove ghost-blog and whishper
Neither is used any more: the blog moves to a self-written site, and
whishper needs more compute than this setup has. Ghost also ran Node 18,
which won't get the eMudhra root store fix.

Drops both apps, the blog DNS record, Gatus check and node001 tunnel
entry, their ca-bundle namespaces, and the leftover ExternalSecret for the
old hensen.io blog namespace. Final Velero backups keep the data:
ghost-blog-final-202610220955 until 22 October 2027 and
whisper-final-202610220955 until 20 January 2027.
2026-10-22 10:11:06 +02:00
Ruben Hensen 8a66913a54 Drop the nas.rubenhensen.nl and alv.rubenhensen.nl ingresses
Neither host has a DNS record, so both were unreachable and cert-manager
has been failing to renew their certificates since 6 April. DSM stays
reachable on the LAN at 192.168.1.99. The nas app only held that ingress
and its ExternalName service, so it goes entirely.
2026-10-22 09:36:26 +02:00
Ruben Hensen 1f736cd4c7 Remove phocas-lustrum
The folder went in April (bb308a3) but the app and its DNS record stayed,
so the demo site kept serving at phocaslustrum.rubenhensen.nl.
2026-10-22 09:36:26 +02:00
Ruben Hensen e5d82b69fd Remove the old in-cluster Stalwart
Its folder went in March (44c31cd) but the Argo CD app stayed and kept the
old hensen.io mail server running, with a NodePort for SMTP/IMAP and a
10Gi volume. Mail runs on node001 now and this one logged nothing in three
days. A final Velero backup (stalwart-final-202610220935) keeps its data
until 20 January 2027. The app has no finalizer, so the namespace gets
deleted by hand.
2026-10-22 09:36:26 +02:00
Ruben Hensen fe678d4b4b ca-bundle: also serve argocd, authentik and actual-budget
Those three namespaces had their own ~190KB copy of patched-ca-bundle.
Let the ca-bundle chart render them too, so the bundle lives in one file.
2026-10-22 09:26:43 +02:00
Ruben Hensen ff73f99d43 velero: name the release resources "velero" so repo maintenance runs
Velero 1.15 builds kopia repository maintenance jobs from a Deployment
called "velero" in its namespace. Ours was velero-helm, so every
BackupRepository reported 'error to build maintenance job: Deployment.apps
"velero" not found' and the repos on the NAS were never cleaned up, some
not since March 2025. fullnameOverride renames the Deployment, Service,
ServiceAccount and RBAC; the old velero-helm objects get deleted by hand
since this app doesn't prune.
2026-10-22 09:23:51 +02:00
Ruben Hensen ea86611deb cert-manager: mount a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). Only the controller, which talks ACME to Let's Encrypt.
2026-10-22 09:13:02 +02:00
Ruben Hensen 7820b8e0bf immich: use a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). The server gets --use-openssl-ca for Node, machine-learning points requests at the bundle instead of certifi.
2026-10-22 09:13:02 +02:00
Ruben Hensen de7ca770a0 whishper: use a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). whishper also gets --use-openssl-ca for Node, and both point requests at the bundle instead of certifi.
2026-10-22 09:13:02 +02:00
Ruben Hensen 767facc5e2 bolletjestrui: use a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). Node uses its built-in roots, so also switch it to OpenSSL's store with --use-openssl-ca.
2026-10-22 09:13:02 +02:00
Ruben Hensen 746cd1283e ghost-blog: use a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). Node uses its built-in roots, so also switch it to OpenSSL's store with --use-openssl-ca.
2026-10-22 09:13:02 +02:00
Ruben Hensen 345055e3e6 serpbear: use a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com). Node uses its built-in roots, so also switch it to OpenSSL's store with --use-openssl-ca.
2026-10-22 09:13:02 +02:00
Ruben Hensen f52b6973e1 gatus: mount a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com).
2026-10-22 09:13:01 +02:00
Ruben Hensen 177dbef15b ntfy: mount a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com).
2026-10-22 09:13:01 +02:00
Ruben Hensen 103aed46ed gitea: mount a CA bundle without the compromised eMudhra roots
Mount patched-ca-bundle (see ca-bundle/) over /etc/ssl/certs so it stops trusting the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com).
2026-10-22 09:13:01 +02:00
Ruben Hensen 9a984c724c Add a ca-bundle chart for the patched CA bundle
Nine more namespaces need patched-ca-bundle, the bundle from Alpine
ca-certificates-bundle 20261020-r0 without the roots above the compromised
eMudhra intermediates. Rather than another nine ~190KB copies, a small
chart renders the ConfigMap from one ca-certificates.crt into every
namespace in values.yaml. argocd, authentik and actual-budget keep their
own copies for now.
2026-10-22 09:11:01 +02:00
Ruben Hensen 3e45ddaf4a Remove lingo
lingo-api ran PHP 8.1.34 (php:8.1-apache) and was reachable at
https://lingo.rubenhensen.nl/api/. PHP 8.1 is EOL and gets no fix for
CVE-2026-109618 and CVE-2026-109619, so it was exposed to the PHP2Shell
RCE. It is no longer used, so drop it entirely: the app, its Gatus
check, the DNS record and the node001 tunnel entry.
2026-10-22 09:06:52 +02:00
Ruben Hensen 842f087da7 mbgwp: start again on PHP 8.3.36
wordpress:7.1.3-php8.3-apache was rebuilt at 15:57 UTC on PHP 8.3.36,
which fixes CVE-2026-109618 and CVE-2026-109619. WordPress core lives on
the volume, so the tag only moves PHP (8.3.30 -> 8.3.36) and Apache. Its
ca-certificates (20250419+deb13u1) no longer carries the roots above the
compromised eMudhra intermediates either.
2026-10-21 20:36:53 +02:00
Ruben Hensen 307bd23500 freshrss: start again on 1.30.3 with fixed PHP
freshrss/freshrss:1.30.3, released today, runs PHP 8.4.27 from Debian
trixie security (8.4.27-1~deb13u1), which fixes CVE-2026-109618 and
CVE-2026-109619. Pin it instead of :latest so the running version is the
checked one. Its ca-certificates (20250419+deb13u1) also no longer
carries the roots above the compromised eMudhra intermediates.
2026-10-21 17:43:08 +02:00
Ruben Hensen 6d9e405126 Point Velero and the NAS services back at 192.168.1.99
Reverts 8c2bd89. The NAS had fallen back to a DHCP address (.10), which
also moved the UniFi controller it hosts away from where the gateway
and access points inform, and left the Longhorn backup target at
nfs://192.168.1.99 unreachable. It now has 192.168.1.99 set statically
in DSM again, so everything that pointed at .99 works without changes.
2026-10-21 15:25:16 +02:00
Ruben Hensen dfdc4451fb velero: raise the server memory limit to 2Gi
At 512Mi the server has been OOMKilled 314 times. With the bucket
reachable again it died 23 seconds into a manual backup of ~14.7k items,
which then got marked Failed on restart. opti1 has 32GB.
2026-10-21 12:33:31 +02:00
Ruben Hensen e19f4b8db5 velero: skip the CRD upgrade hook
The hook's init container pulls docker.io/bitnami/kubectl:1.32, which
Bitnami has removed, so the sync for the new NAS address hung on
ImagePullBackOff. The chart stays at 8.4.0 and the CRDs are already in
place.
2026-10-21 12:22:57 +02:00
Ruben Hensen 8c2bd89444 Point Velero and the NAS services at 192.168.1.10
The NAS moved from 192.168.1.99 to .10, so the backup storage location
has been Unavailable ("no route to host"). Every backup since at least
26 July failed, and 154 expired ones are stuck in Deleting because Velero
can't reach the bucket to remove them. MinIO answers on .10:9000 and DSM
on .10:5000.
2026-10-21 12:16:19 +02:00
Ruben Hensen 400d46c462 actual-budget: use a CA bundle without the compromised eMudhra roots
Node uses its built-in roots, which still include emSign ECC Root CA - G3,
and the Node fix is still pending. Switch to OpenSSL's store with
--use-openssl-ca and point it at patched-ca-bundle, mounted over
/etc/ssl/certs. That covers bank sync and the authentik OIDC calls.
2026-10-21 12:09:41 +02:00
Ruben Hensen 25a6bf3a05 authentik: mount a CA bundle without the compromised eMudhra roots
Server and worker trusted the leaked eMudhra intermediates through the
Debian bundle (ca-certificates 20250419), Python's ssl module and certifi
2026.01.04. Mount patched-ca-bundle over /etc/ssl/certs and point
SSL_CERT_FILE and REQUESTS_CA_BUNDLE at it until an authentik image ships
a fixed bundle and certifi.
2026-10-21 12:09:41 +02:00
Ruben Hensen a507282103 argocd: mount a CA bundle without the compromised eMudhra roots
The Argo CD v2.14.2 image (Ubuntu 24.04, ca-certificates 20240203) and the
dex image still trust the eMudhra intermediates whose keys leaked
(https://emudhra.we-have-a-problem.com), and the repo server fetches git
and Helm repos over that trust store. A forged certificate there means
arbitrary manifests in the cluster.

patched-ca-bundle holds the bundle from Alpine ca-certificates-bundle
20261020-r0 and replaces /etc/ssl/certs in every Argo CD container except
redis. The whole directory goes, since OpenSSL and Go also read the
per-root files next to ca-certificates.crt. It uses server-side apply to
keep the bundle out of the last-applied annotation.
2026-10-21 12:09:41 +02:00
Ruben Hensen 19eacd35f7 Remove ip-updater
Every run has failed with "Permission denied (publickey)" on
root@46.224.26.65, the last successful job was 219 days ago, and one pod
had been hanging for 138 days. The home IP is pinned in
nix-infra-machine/nodes/node001.nix instead, so nothing used it.

It also ran alpine:3.19, which is EOL and still trusts the compromised
eMudhra intermediates.
2026-10-21 11:49:28 +02:00
Ruben Hensen bb7e2f2bac node001: distrust the roots above the compromised eMudhra intermediates
The private keys of eight eMudhra intermediates are recoverable
(https://emudhra.we-have-a-problem.com). node001 runs NixOS 25.11 from
March with nss-cacert 3.121, and curl there still accepted a chain via
emSign ECC Root CA - G3. Blacklist that root and Comodo AAA Services root
until nixpkgs ships NSS 3.131.1. Everything node001 talks to chains to
ISRG Root X1.

Already deployed with ./cli update node001, and Gatus, ntfy and Stalwart
were restarted so they reload the trust store.
2026-10-21 11:49:28 +02:00
Ruben Hensen 1efa132f9d Stop FreshRSS + MBG WordPress until PHP is patched
CERT-EU 2026-018 (CVE-2026-109618, CVE-2026-109619, CVSS 9.2): possible
unauthenticated RCE in PHP 5 and later. Both are internet-facing and are
the only PHP workloads (FreshRSS on PHP 8.2.29, WordPress on 8.3.30), so
scale them to 0 until their images ship a fixed PHP. PVCs and the MariaDB
cluster stay as they are.
2026-10-21 09:18:24 +02:00
Ruben Hensen 054117ad6d vault: point External Secrets at the in-cluster Vault service
The store went through https://vault.rubenhensen.nl, so via Hetzner and
the home internet connection. When home internet dropped, the store
validation failed and External Secrets backed off long enough that it
needed a controller restart after the connection came back.

vault-active.vault.svc talks to the active Vault pod directly. It's plain
HTTP, same as the ingress → Vault hop already is.
2026-10-20 15:45:55 +02:00
Ruben Hensen ac61c346af node001: run ntfy at ntfy1.rubenhensen.nl and alert from s1
ntfy listens on 127.0.0.1:2586 behind the same SNI-to-8444 setup as s1.
Users and tokens come from encrypted nix-infra secrets, exported as env
vars by a small wrapper since ntfy and Gatus only read them from the
environment.

s1 alerts on the home services, Scouting MBG and s2. It stays quiet on
mail, which lives on this box and is covered by s2.
2026-10-20 15:34:42 +02:00
Ruben Hensen e23779044f gatus: alert through self-hosted ntfy
Add ntfy at ntfy2.rubenhensen.nl on the home cluster, pointed straight at
the home IP like s2. s2 now alerts on mail and on s1 through it. The
home services are left to s1, which sees them from outside.

ntfy denies everything except the provisioned user. The user, its
password hash and the Gatus token come from Vault kv/ntfy.
2026-10-20 15:34:42 +02:00
Ruben Hensen 53a079dc22 node001: run Gatus at s1.rubenhensen.nl
Gatus listens on 127.0.0.1:8090. nginx gets s1 in the SNI map, sends it
to a local TLS vhost on 8444 with its own ACME cert, and proxies to
Gatus from there. The endpoint list is built from tunneledHosts plus
mail, Scouting MBG and s2, matching gatus/config.yaml.
2026-10-20 11:03:58 +02:00
Ruben Hensen 3ffb10b627 gatus: add s2.rubenhensen.nl status page on the home cluster
Gatus with sqlite history, checking every public service plus its twin
s1.rubenhensen.nl on Hetzner. Replaces the GitHub-hosted Upptime page.

DNS gets s1 (Hetzner) and s2. s2 points straight at the home IP rather
than through the Hetzner tunnel, so it stays reachable when Hetzner is
down.

gatus/README.md explains how to read the two pages and writes down the
plan for a single self-hosted failover URL (PowerDNS LUA records).
2026-10-20 11:03:58 +02:00
Ruben Hensen 145f4eaac4 gitea: pin to 1.27.3 (CVE-2026-60004, CVE-2026-20896, CVE-2026-27771)
The floating gitea/gitea:1 tag with IfNotPresent pull policy left the
node on a cached 1.26.1 image. Pin the version and let Renovate track it.
2026-09-24 11:40:12 +02:00
Ruben Hensen 20cf119dbd Extend authentik + FreshRSS session lifetimes
Authentik's default-authentication-login stage ships with
session_duration: seconds=0, so the SSO session died with the browser.
New blueprint raises it to 30 days for every app on that flow.

FreshRSS runs OIDC through Apache mod_auth_openidc, whose defaults are a
5 minute inactivity timeout and a ~7.5 hour max duration in a non-persistent
cookie. Bumped to a 30 day sliding inactivity window (refreshed on every
request) with a 90 day hard cap, and made the cookie persistent so it
survives a browser restart.
2026-09-03 15:21:07 +02:00
Ruben Hensen ec5405fc29 bolletjestrui: deploy main-10268f1 (routes, voting, push, ride uploads)
Adds the VAPID keypair for web push and raises the ingress body limit to 25m to
match the app's BODY_SIZE_LIMIT, since a bulk route import posts every GPX in one
request.

The VAPID env refs are optional:true on purpose — a missing key in a secretKeyRef
puts the pod in CreateContainerConfigError, and the app already handles absent
keys by sending no notifications.
2026-08-15 17:55:37 +02:00
Ruben Hensen b50f8dc5b6 bolletjestrui: deploy main-8f17b5d (editable etappe titles) 2026-07-24 11:36:21 +02:00
Ruben Hensen 06dd19e5de bolletjestrui: deploy main-878b462 (select chevron fix) 2026-07-24 11:13:54 +02:00
Ruben Hensen 29847b1f12 bolletjestrui: deploy main-cca932c (global scoring setting) 2026-07-24 10:55:50 +02:00
Ruben Hensen 52b58835c0 bolletjestrui: deploy main-b3bfe55 + BODY_SIZE_LIMIT 25M (20MB profile photos) 2026-07-23 23:20:57 +02:00
Ruben Hensen 1d7d625d53 bolletjestrui: deploy main-7e1236d (mobile hamburger menu) 2026-07-23 22:27:43 +02:00
Ruben Hensen a3dadcd50f bolletjestrui: deploy main-923b40f (climb-matching CSV streams fix) 2026-07-23 21:09:47 +02:00
Ruben Hensen 095d82af02 bolletjestrui: bump image to main-60c604c 2026-07-22 12:08:41 +02:00
Ruben Hensen aabe5ad349 bolletjestrui: bump image to main-1a46d10 2026-07-22 11:55:40 +02:00
Ruben Hensen 851f9e4a20 bolletjestrui: bump image to main-041b4e0 2026-07-22 11:40:52 +02:00
Ruben Hensen 0b5eb69f84 bolletjestrui: bump image to main-1e286f5 2026-07-22 11:31:41 +02:00
Ruben Hensen 15d7916e81 bolletjestrui: bump image to main-d21edde 2026-07-22 11:03:46 +02:00
Ruben Hensen d2f5d5eac6 bolletjestrui: bump image to main-86048a8
Even more generous detection; NC climbs now score a point.
2026-07-21 16:53:18 +02:00
Ruben Hensen c0b4a7183b bolletjestrui: bump image to main-b5baf1f
Generous climb detection (min length/grade/score lowered, Cat 4 floor)
and the climb category editor fix.
2026-07-21 16:36:59 +02:00
Ruben Hensen 8e60f6796a node001: tunnel vic.rubenhensen.nl to the home cluster
Add vic.rubenhensen.nl to tunneledHosts so the edge box does SNI
passthrough on :443 and the :80 ACME/redirect vhost for it, matching
the DNS record. Without this, vic falls through to Stalwart on :8443
and cert-manager's HTTP-01 challenge can't be reached.
2026-07-21 15:29:49 +02:00
Ruben Hensen f13417bc8f Add bolletjestrui app + vic.rubenhensen.nl
Deploys ghcr.io/rubenhensen/bolletjestrui at vic.rubenhensen.nl:
- bolletjestrui/ folder: deployment (SQLite on a PVC, migrate-on-start,
  ORIGIN + raised BODY_SIZE_LIMIT for GPX uploads), service, nginx
  ingress with prod-cluster-issuer TLS, PVC, and a Vault ExternalSecret
  (kv/bolletjestrui: site_password, admin_password, key_secret).
- apps/templates/bolletjestrui-folder.yaml: ArgoCD Application.
- dns: vic A record -> 46.224.26.65 (ingress LB).
- renovate: watch bolletjestrui/ for image tag bumps.

Committed locally, not pushed: needs the Vault secret created and the
ghcr package made public first.
2026-07-21 14:33:31 +02:00
Ruben Hensen a11309263e Update home cluster IP to 62.41.86.27 2026-06-06 09:52:36 +02:00
Ruben Hensen 379c050bb3 Update actual-budget to chart 1.8.9 / app 26.6.0 2026-06-03 11:28:10 +02:00
Ruben Hensen 20128bcd73 Add gitea at git.rubenhensen.nl
Single-pod sqlite install (simplest path for a home git host). HTTPS-only,
no SSH listener for now. Wired into the Hetzner tunnel like the other
rubenhensen.nl services.

First visitor to git.rubenhensen.nl can register; Gitea auto-promotes the
first user to admin.
2026-05-19 23:19:21 +02:00
Ruben Hensen ffe8830b5e Tunnel argocd/ha/longhorn/lingo/blog/serpbear through Hetzner
Refactor node001 nginx to drive both the SNI map and the port-80 vhosts
from a single tunneledHosts list so adding a service is one line.
2026-05-19 23:14:04 +02:00
Ruben Hensen 8d383d4261 Tunnel ynab.rubenhensen.nl through Hetzner 2026-05-19 23:04:02 +02:00
Ruben Hensen 00d46b6bd6 Tunnel vault.rubenhensen.nl through Hetzner 2026-05-19 22:56:52 +02:00
Ruben Hensen cb7cba25d0 Tunnel authentik.rubenhensen.nl through Hetzner
Same pattern as rss — needed so the OIDC redirect from freshrss (and
other relying parties) works for clients outside the home LAN.
2026-05-19 22:50:56 +02:00
Ruben Hensen ff9c2d3cef Tunnel rss.rubenhensen.nl through Hetzner
Point rss to the Hetzner box and reverse-proxy/SNI-passthrough back to
the home cluster so cert-manager keeps owning the certificate. Move
stalwart's HTTPS listener to 127.0.0.1:8443 so nginx can take :443 and
dispatch by SNI.
2026-05-19 22:45:55 +02:00
Ruben Hensen 790d7d6f32 Add WF_ENCRYPTION_KEY to mbgwp wordpress 2026-05-18 22:12:45 +02:00
Ruben Hensen 8aef769e78 Fix serpbear PVC permissions 2026-04-25 20:48:27 +02:00
269 changed files with 10624 additions and 8254 deletions

No files matched your search

+56
View File
@@ -0,0 +1,56 @@
# Renders every Argo CD app the way Argo CD does and validates the result
# (tools/ci/validate.py), so a broken manifest or a Renovate bump that no
# longer renders shows up on the PR instead of in a failed sync.
name: validate
on:
pull_request:
push:
branches: [main]
workflow_dispatch:
permissions:
contents: read
concurrency:
group: validate-${{ github.ref }}
cancel-in-progress: true
jobs:
validate:
runs-on: ubuntu-24.04
timeout-minutes: 20
steps:
- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
- name: Install helm, kustomize and kubeconform
env:
# Helm 4.2, like Argo CD 3.5.
# renovate: datasource=github-releases depName=helm/helm
HELM_VERSION: v4.2.1
# renovate: datasource=github-releases depName=kubernetes-sigs/kustomize extractVersion=^kustomize/(?<version>.+)$
KUSTOMIZE_VERSION: v5.8.3
# renovate: datasource=github-releases depName=yannh/kubeconform
KUBECONFORM_VERSION: v0.8.0
run: |
set -euo pipefail
cd "$RUNNER_TEMP"
curl -sSfLO "https://get.helm.sh/helm-${HELM_VERSION}-linux-amd64.tar.gz"
curl -sSfL "https://get.helm.sh/helm-${HELM_VERSION}-linux-amd64.tar.gz.sha256sum" | sha256sum -c -
k="https://github.com/kubernetes-sigs/kustomize/releases/download/kustomize%2F${KUSTOMIZE_VERSION}"
curl -sSfLO "$k/kustomize_${KUSTOMIZE_VERSION}_linux_amd64.tar.gz"
curl -sSfL "$k/checksums.txt" | grep " kustomize_${KUSTOMIZE_VERSION}_linux_amd64.tar.gz$" | sha256sum -c -
c="https://github.com/yannh/kubeconform/releases/download/${KUBECONFORM_VERSION}"
curl -sSfLO "$c/kubeconform-linux-amd64.tar.gz"
curl -sSfL "$c/CHECKSUMS" | grep " kubeconform-linux-amd64.tar.gz$" | sha256sum -c -
mkdir -p bin
tar xzf "helm-${HELM_VERSION}-linux-amd64.tar.gz" -C bin --strip-components=1 linux-amd64/helm
tar xzf "kustomize_${KUSTOMIZE_VERSION}_linux_amd64.tar.gz" -C bin kustomize
tar xzf kubeconform-linux-amd64.tar.gz -C bin kubeconform
echo "$RUNNER_TEMP/bin" >> "$GITHUB_PATH"
pip install --quiet pyyaml==6.0.3
- name: Render and validate
run: python3 tools/ci/validate.py
+1
View File
@@ -6,3 +6,4 @@ velero-credentials
nix-infra-machine/ssh/
nix-infra-machine/.env
nix-infra-machine/nix/
.DS_Store
+16
View File
@@ -0,0 +1,16 @@
# The TLS certificate the Gateway serves for this app (see httproute.yaml).
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: actual-budget-tls
spec:
secretName: actual-budget-tls
dnsNames:
- ynab.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
+1 -1
View File
@@ -1,4 +1,4 @@
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: actualbudget-oidc-client-secret
+16 -19
View File
@@ -12,14 +12,14 @@ spec:
project: default
source:
repoURL: https://community-charts.github.io/helm-charts
targetRevision: 1.8.7
targetRevision: 1.8.9
chart: actualbudget
helm:
values: |
# Actual Budget configuration
image:
tag: "26.3.0"
tag: "26.6.0"
# Authentication configuration
login:
@@ -36,29 +36,26 @@ spec:
extraEnvVars:
ACTUAL_OPENID_SERVER_HOSTNAME: https://ynab.rubenhensen.nl
# Node trusts its built-in roots, which still include the ones
# above the compromised eMudhra intermediates. Use patched-ca-bundle
# through OpenSSL instead until Node ships a fix.
NODE_OPTIONS: --use-openssl-ca
SSL_CERT_FILE: /etc/ssl/certs/ca-certificates.crt
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
# Service configuration
service:
type: ClusterIP
port: 5006
# Ingress configuration
ingress:
enabled: true
className: nginx
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/proxy-body-size: 50m
hosts:
- host: ynab.rubenhensen.nl
paths:
- path: /
pathType: Prefix
tls:
- secretName: actual-budget-tls
hosts:
- ynab.rubenhensen.nl
# Persistence configuration
persistence:
enabled: true
+34
View File
@@ -0,0 +1,34 @@
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: actual-budget
spec:
parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: https-ynab
hostnames:
- ynab.rubenhensen.nl
rules:
- backendRefs:
- name: helm-actual-budget-actualbudget
port: 5006
# No limit on the whole request, as with nginx. Envoy's default of 15s
# cuts off uploads and long-lived connections.
timeouts:
request: 0s
---
# Lets the Gateway serve the certificate cert-manager keeps in this namespace.
apiVersion: gateway.networking.k8s.io/v1
kind: ReferenceGrant
metadata:
name: gateway-tls
spec:
from:
- group: gateway.networking.k8s.io
kind: Gateway
namespace: envoy-gateway-system
to:
- group: ""
kind: Secret
name: actual-budget-tls
+57
View File
@@ -0,0 +1,57 @@
# Actual faces the internet through Envoy, so its pods only reach each
# other, DNS and the internet: not the LAN (NAS, router), the Kubernetes
# API or other namespaces.
# The OIDC login goes through authentik's public address.
# Ingress comes from Envoy and the node itself (kubelet probes; 10.1.7.64
# is the node's Calico VXLAN address, projectcalico.org/IPv4VXLANTunnelAddr).
# Same layout as mbgwp/networkpolicy.yaml.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default
spec:
podSelector: {}
policyTypes:
- Ingress
- Egress
ingress:
- from:
- podSelector: {}
- from:
- ipBlock:
cidr: 192.168.1.204/32
- ipBlock:
cidr: 10.1.7.64/32
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: envoy-gateway-system
podSelector:
matchLabels:
app.kubernetes.io/name: envoy
ports:
- port: 5006
egress:
- to:
- podSelector: {}
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: kube-dns
ports:
- protocol: UDP
port: 53
- protocol: TCP
port: 53
- to:
- ipBlock:
cidr: 0.0.0.0/0
except:
- 10.0.0.0/8
- 100.64.0.0/10
- 169.254.0.0/16
- 172.16.0.0/12
- 192.168.0.0/16
+6
View File
@@ -2,6 +2,9 @@ apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: argocd-folder
annotations:
# Let the API server fill in Gateway API defaults before diffing.
argocd.argoproj.io/compare-options: ServerSideDiff=true
spec:
project: default
source:
@@ -14,5 +17,8 @@ spec:
syncPolicy:
syncOptions:
- CreateNamespace=true
# From Argo CD 3.3 the ApplicationSet CRD is too big for client-side
# apply's last-applied annotation.
- ServerSideApply=true
automated:
selfHeal: true
+113 -18
View File
@@ -16,7 +16,7 @@ spec:
sources:
- chart: authentik
repoURL: https://charts.goauthentik.io
targetRevision: 2026.2.1
targetRevision: 2026.8.5
helm:
values: |
authentik:
@@ -86,8 +86,27 @@ spec:
secretKeyRef:
name: actualbudget-oidc-client-secret
key: client_secret
- name: LONGHORN_OIDC_CLIENT_SECRET
valueFrom:
secretKeyRef:
name: longhorn-oidc-client-secret
key: client_secret
# Point OpenSSL and requests (which uses certifi otherwise) at
# patched-ca-bundle, mounted below until the image drops the
# compromised eMudhra intermediates.
- name: SSL_CERT_FILE
value: /etc/ssl/certs/ca-certificates.crt
- name: REQUESTS_CA_BUNDLE
value: /etc/ssl/certs/ca-certificates.crt
server:
resources:
requests:
cpu: 70m
memory: 560Mi
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
- name: blueprint-vault
configMap:
name: authentik-blueprint-vault
@@ -106,6 +125,35 @@ spec:
- name: blueprint-actualbudget
configMap:
name: authentik-blueprint-actualbudget
- name: blueprint-session
configMap:
name: authentik-blueprint-session
- name: blueprint-longhorn
configMap:
name: authentik-blueprint-longhorn
# Directory mounts, not subPath, so changes reach the pods
# without a restart. The secrets are optional: a blueprint
# that needs a missing one fails until it shows up.
- name: blueprint-scouting
configMap:
name: authentik-blueprint-scouting
- name: scouting-secrets
projected:
sources:
- secret:
name: immich-oidc-client-secret
optional: true
items:
- key: client_secret
path: immich-oidc-client-secret
- secret:
name: scouts-online-client
optional: true
items:
- key: client_id
path: scouts-online-client-id
- key: client_secret
path: scouts-online-client-secret
volumeMounts:
- name: blueprint-vault
mountPath: /blueprints/custom/vault-oidc.yaml
@@ -125,19 +173,29 @@ spec:
- name: blueprint-actualbudget
mountPath: /blueprints/custom/actualbudget-proxy.yaml
subPath: actualbudget-proxy.yaml
ingress:
enabled: true
ingressClassName: nginx
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
hosts:
- authentik.rubenhensen.nl
tls:
- secretName: authentik-tls
hosts:
- authentik.rubenhensen.nl
- name: blueprint-session
mountPath: /blueprints/custom/session-duration.yaml
subPath: session-duration.yaml
- name: blueprint-longhorn
mountPath: /blueprints/custom/longhorn-oidc.yaml
subPath: longhorn-oidc.yaml
- name: blueprint-scouting
mountPath: /blueprints/custom/scouting
- name: scouting-secrets
mountPath: /secrets/scouting
readOnly: true
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
worker:
resources:
requests:
cpu: 100m
memory: 336Mi
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
- name: blueprint-vault
configMap:
name: authentik-blueprint-vault
@@ -156,6 +214,35 @@ spec:
- name: blueprint-actualbudget
configMap:
name: authentik-blueprint-actualbudget
- name: blueprint-session
configMap:
name: authentik-blueprint-session
- name: blueprint-longhorn
configMap:
name: authentik-blueprint-longhorn
# Directory mounts, not subPath, so changes reach the pods
# without a restart. The secrets are optional: a blueprint
# that needs a missing one fails until it shows up.
- name: blueprint-scouting
configMap:
name: authentik-blueprint-scouting
- name: scouting-secrets
projected:
sources:
- secret:
name: immich-oidc-client-secret
optional: true
items:
- key: client_secret
path: immich-oidc-client-secret
- secret:
name: scouts-online-client
optional: true
items:
- key: client_id
path: scouts-online-client-id
- key: client_secret
path: scouts-online-client-secret
volumeMounts:
- name: blueprint-vault
mountPath: /blueprints/custom/vault-oidc.yaml
@@ -175,14 +262,22 @@ spec:
- name: blueprint-actualbudget
mountPath: /blueprints/custom/actualbudget-proxy.yaml
subPath: actualbudget-proxy.yaml
- name: blueprint-session
mountPath: /blueprints/custom/session-duration.yaml
subPath: session-duration.yaml
- name: blueprint-longhorn
mountPath: /blueprints/custom/longhorn-oidc.yaml
subPath: longhorn-oidc.yaml
- name: blueprint-scouting
mountPath: /blueprints/custom/scouting
- name: scouting-secrets
mountPath: /secrets/scouting
readOnly: true
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
postgresql:
enabled: false
redis:
enabled: true
master:
persistence:
storageClass: longhorn
size: 2Gi
- repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: authentik
@@ -1,21 +1,21 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: phocas-lustrum
name: bolletjestrui
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: phocas-lustrum
path: bolletjestrui
destination:
server: https://kubernetes.default.svc
namespace: phocas-lustrum
namespace: bolletjestrui
syncPolicy:
syncOptions:
- CreateNamespace=true
- CreateNamespace=true
automated:
selfHeal: true
@@ -1,7 +1,7 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: ip-updater
name: ca-bundle
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
@@ -10,13 +10,12 @@ spec:
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: ip-updater
path: ca-bundle
destination:
server: https://kubernetes.default.svc
namespace: ip-updater
# Every ConfigMap sets its own namespace.
namespace: argocd
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
prune: true
+31 -1
View File
@@ -12,12 +12,42 @@ spec:
project: default
source:
repoURL: https://charts.jetstack.io
targetRevision: v1.15.5
targetRevision: v1.21.3
chart: cert-manager
helm:
parameters:
- name: crds.enabled
value: 'true'
# The controller talks ACME to Let's Encrypt. Give it a trust store
# without the compromised eMudhra intermediates, see ca-bundle/.
values: |
# Lets cert-manager solve HTTP-01 challenges with an HTTPRoute on
# the Gateway, see cert-manager/prod-cluster-issuer.yaml.
config:
gatewayAPI:
enabled: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
resources:
requests:
cpu: 10m
memory: 48Mi
cainjector:
resources:
requests:
cpu: 10m
memory: 80Mi
webhook:
resources:
requests:
cpu: 10m
memory: 32Mi
syncPolicy:
syncOptions:
- CreateNamespace=true
+16 -2
View File
@@ -10,10 +10,24 @@ spec:
source:
chart: cloudnative-pg
repoURL: https://cloudnative-pg.github.io/charts
targetRevision: 0.23.2
targetRevision: 0.29.1
helm:
values: |
# Default values are fine
config:
data:
# Swap the instance manager inside running pods on operator
# upgrades instead of restarting them. Both clusters have a
# single instance, so a restart means downtime.
ENABLE_INSTANCE_MANAGER_INPLACE_UPDATES: "true"
# Ride out dqlite stalls of up to ~40s instead of restarting when a
# lease renewal takes over 10s (docs/upgrade-k8s-1.33.md).
additionalArgs:
- --leader-lease-duration=60
- --leader-renew-deadline=40
resources:
requests:
cpu: 10m
memory: 48Mi
destination:
server: https://kubernetes.default.svc
namespace: cnpg-system
+39
View File
@@ -0,0 +1,39 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: helm-envoy-gateway
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
# No scheme, so Argo CD pulls the chart from the OCI registry.
repoURL: docker.io/envoyproxy
chart: gateway-helm
# v1.9 supports Kubernetes 1.33 to 1.36
targetRevision: v1.9.2
helm:
values: |
config:
envoyGateway:
provider:
kubernetes:
# Ride out dqlite stalls of up to ~40s instead of restarting
# when a lease renewal takes over 10s
# (docs/upgrade-k8s-1.33.md).
leaderElection:
leaseDuration: 60s
renewDeadline: 40s
retryPeriod: 5s
destination:
server: https://kubernetes.default.svc
namespace: envoy-gateway-system
syncPolicy:
syncOptions:
- CreateNamespace=true
# The bundled Gateway API CRDs are too big for client-side apply.
- ServerSideApply=true
automated:
prune: true
selfHeal: true
+20 -2
View File
@@ -8,14 +8,32 @@ metadata:
spec:
syncPolicy:
syncOptions:
- CreateNamespace=true
- CreateNamespace=true
# From 0.19 the ESO CRDs are too big for client-side apply.
- ServerSideApply=true
automated:
selfHeal: true
project: default
sources:
- chart: external-secrets
repoURL: https://charts.external-secrets.io
targetRevision: 0.10.7
targetRevision: 2.14.0
helm:
values: |
resources:
requests:
cpu: 20m
memory: 64Mi
certController:
resources:
requests:
cpu: 10m
memory: 64Mi
webhook:
resources:
requests:
cpu: 10m
memory: 32Mi
destination:
server: https://kubernetes.default.svc
namespace: external-secrets
+26
View File
@@ -0,0 +1,26 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: gateway-folder
namespace: argocd
annotations:
# Let the API server fill in Gateway API defaults before diffing, or
# every defaulted field shows up as a difference.
argocd.argoproj.io/compare-options: ServerSideDiff=true
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: gateway
destination:
server: https://kubernetes.default.svc
namespace: envoy-gateway-system
syncPolicy:
syncOptions:
- ServerSideApply=true
automated:
prune: true
selfHeal: true
+24
View File
@@ -0,0 +1,24 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: gatus-folder
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: gatus
destination:
server: https://kubernetes.default.svc
namespace: gatus
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
# Each config change generates a new gatus-config-<hash> ConfigMap;
# prune removes the old one.
prune: true
selfHeal: true
@@ -1,7 +1,7 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: lingo
name: gitea
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
@@ -10,10 +10,10 @@ spec:
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: lingo
path: gitea
destination:
server: https://kubernetes.default.svc
namespace: lingo
namespace: gitea
syncPolicy:
syncOptions:
- CreateNamespace=true
+30 -1
View File
@@ -5,6 +5,10 @@ metadata:
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
# Argo CD 3.x adds these for apps with PreDelete hooks (the Longhorn
# chart has one). Listed here so the parent app doesn't see a diff.
- pre-delete-finalizer.argocd.argoproj.io
- pre-delete-finalizer.argocd.argoproj.io/cleanup
spec:
syncPolicy:
syncOptions:
@@ -16,13 +20,38 @@ spec:
sources:
- chart: longhorn
repoURL: https://charts.longhorn.io/
targetRevision: 1.7.3 # Replace with the Longhorn version you'd like to install or upgrade to
# One minor at a time; each upgrade moves every volume to the new
# engine image before the next.
targetRevision: 1.13.0
helm:
values: |
persistence:
defaultClassReplicaCount: 1
preUpgradeChecker:
jobEnabled: false
# restrictInternalTraffic is on by default since 1.12: only Longhorn
# components may reach the longhorn-manager API (otherwise any pod
# could manage volumes unauthenticated). Since 1.13 iSCSI (3260)
# stays open to the host-side initiator.
# From 1.13 the CSI controller may read every Secret in the cluster,
# for provisioner-secret StorageClass parameters. Neither
# StorageClass here uses those.
csi:
allowControllerSecretAccess: false
# New in 1.13, three replicas by default; this cluster has one node.
longhornGlobalManager:
replicas: 1
# Since 1.8 the backup target is a BackupTarget resource instead of
# the backup-target setting.
defaultBackupStore:
backupTarget: nfs://192.168.1.99:/volume1/microk8s-nfs
# Every poll rewrites the backupvolume objects, about 8% of all
# datastore writes at 300s. Backups only run nightly.
pollInterval: 1800
defaultSettings:
# Move volumes to the new engine image after each Longhorn
# upgrade, one at a time. At 0 they stayed behind on 1.7.1/1.7.2.
concurrentAutomaticEngineUpgradePerNodeLimit: 1
parameters:
- name: csi.kubeletRootDir
value: "/var/snap/microk8s/common/var/lib/kubelet"
+27 -26
View File
@@ -12,15 +12,17 @@ spec:
project: default
source:
repoURL: https://groundhog2k.github.io/helm-charts/
targetRevision: 0.15.0
targetRevision: 0.16.7
chart: wordpress
helm:
values: |
# Official WordPress image configuration
# Official WordPress image configuration. WordPress core lives on the
# volume, so the tag only sets PHP and Apache; 7.1.3-php8.3-apache
# ships PHP 8.3.36, which fixes CVE-2026-109618 and CVE-2026-109619.
image:
registry: docker.io
repository: wordpress
tag: "6.9.1-apache"
tag: "7.1.3-php8.3-apache"
pullPolicy: IfNotPresent
# Disable embedded MariaDB
@@ -41,6 +43,11 @@ spec:
secretKeyRef:
name: mbgwp-mariadb-credentials
key: password
- name: WF_ENCRYPTION_KEY
valueFrom:
secretKeyRef:
name: wordpress-credentials
key: wf-encryption-key
# WordPress specific settings
settings:
@@ -61,29 +68,6 @@ spec:
type: ClusterIP
port: 80
# Ingress configuration
ingress:
enabled: true
className: nginx
maxBodySize: 1024m
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/proxy-body-size: 1G
hosts:
- host: scoutingmbg.nl
paths:
- path: /
pathType: Prefix
- host: www.scoutingmbg.nl
paths:
- path: /
pathType: Prefix
tls:
- secretName: scoutingmbg-nl-tls
hosts:
- scoutingmbg.nl
- www.scoutingmbg.nl
# Resource limits (matching Bitnami "small" preset)
resources:
requests:
@@ -117,6 +101,23 @@ spec:
timeoutSeconds: 5
failureThreshold: 30
# apache2.conf includes ports.conf after mods-enabled/*.conf, so the
# prefork settings here replace mpm_prefork.conf's MaxRequestWorkers
# 150. A worker takes ~45-60 MB (PSS), so 150 never fit in 1Gi: a
# crawler asking for 88 pages at once got the container OOMKilled on
# 2026-10-25. With 12 workers a burst waits in the listen backlog
# instead. Listen is the chart's default (containerPort).
apachePortsConfig: |
Listen 8000
<IfModule mpm_prefork_module>
StartServers 4
MinSpareServers 2
MaxSpareServers 6
ServerLimit 12
MaxRequestWorkers 12
MaxConnectionsPerChild 1000
</IfModule>
# Custom PHP configuration
customPhpConfig: |
upload_max_filesize = 64M
+34
View File
@@ -0,0 +1,34 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: metrics-server
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
chart: metrics-server
repoURL: https://kubernetes-sigs.github.io/metrics-server/
targetRevision: 3.14.0
helm:
values: |
# Resource usage for kubectl top and for sizing requests and limits.
# It keeps everything in memory, so it adds no writes to the SSD.
args:
# microk8s's kubelet serves a self-signed certificate; its own
# metrics-server addon passes the same flag.
- --kubelet-insecure-tls
resources:
requests:
cpu: 20m
memory: 64Mi
limits:
memory: 256Mi
destination:
server: https://kubernetes.default.svc
namespace: kube-system
syncPolicy:
automated:
prune: true
selfHeal: true
-21
View File
@@ -1,21 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: nas
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: nas
destination:
server: https://kubernetes.default.svc
namespace: nas
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
@@ -1,7 +1,7 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: ghost-blog
name: ntfy-folder
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
@@ -10,10 +10,10 @@ spec:
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: ghost-blog
path: ntfy
destination:
server: https://kubernetes.default.svc
namespace: ghost-blog
namespace: ntfy
syncPolicy:
syncOptions:
- CreateNamespace=true
-21
View File
@@ -1,21 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: secrets-folder
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: secrets
destination:
server: https://kubernetes.default.svc
namespace: secrets
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
+19 -4
View File
@@ -7,16 +7,31 @@ spec:
project: default
source:
repoURL: https://github.com/kubernetes-csi/external-snapshotter.git
targetRevision: v8.2.1
targetRevision: v8.7.0
path: deploy/kubernetes/snapshot-controller
kustomize:
patches:
# Ride out dqlite stalls of up to ~40s instead of restarting when a
# lease renewal takes over 10s (docs/upgrade-k8s-1.33.md).
- target:
kind: Deployment
name: snapshot-controller
patch: |-
- op: add
path: /spec/template/spec/containers/0/args/-
value: --leader-election-lease-duration=60s
- op: add
path: /spec/template/spec/containers/0/args/-
value: --leader-election-renew-deadline=40s
- op: add
path: /spec/template/spec/containers/0/args/-
value: --leader-election-retry-period=5s
destination:
server: https://kubernetes.default.svc
namespace: kube-system
syncPolicy:
# Was listed twice, with and without prune; Argo CD kept the last one.
automated:
selfHeal: true
prune: true
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
-22
View File
@@ -1,22 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: stalwart
namespace: argocd
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: stalwart
destination:
server: https://kubernetes.default.svc
namespace: stalwart
syncPolicy:
automated:
selfHeal: true
prune: true
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
-21
View File
@@ -1,21 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: whisper
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: whishper
destination:
server: https://kubernetes.default.svc
namespace: whisper
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
+16
View File
@@ -0,0 +1,16 @@
# The TLS certificate the Gateway serves for this app (see httproute.yaml).
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: letsencrypt-prod
spec:
secretName: letsencrypt-prod
dnsNames:
- argocd.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
+34
View File
@@ -0,0 +1,34 @@
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: argocd
spec:
parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: https-argocd
hostnames:
- argocd.rubenhensen.nl
rules:
- backendRefs:
- name: argocd-server
port: 80
# No limit on the whole request, as with nginx. Envoy's default of 15s
# cuts off uploads and long-lived connections.
timeouts:
request: 0s
---
# Lets the Gateway serve the certificate cert-manager keeps in this namespace.
apiVersion: gateway.networking.k8s.io/v1
kind: ReferenceGrant
metadata:
name: gateway-tls
spec:
from:
- group: gateway.networking.k8s.io
kind: Gateway
namespace: envoy-gateway-system
to:
- group: ""
kind: Secret
name: letsencrypt-prod
-31
View File
@@ -1,31 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: argocd-server-ingress
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
# If you encounter a redirect loop or are getting a 307 response code
# then you need to force the nginx ingress to connect to the backend using HTTPS.
#
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
namespace: argocd
spec:
ingressClassName: nginx
rules:
- host: argocd.rubenhensen.nl
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: argocd-server
port:
name: https
tls:
- secretName: letsencrypt-prod
hosts:
- argocd.rubenhensen.nl
+8 -4
View File
@@ -4,10 +4,11 @@ kind: Kustomization
namespace: argocd
# additional resources like ingress rules, cluster and repository secrets.
# additional resources like the route, certificate and secrets.
resources:
- https://raw.githubusercontent.com/argoproj/argo-cd/refs/tags/v2.14.2/manifests/install.yaml
- ingress.yaml
- https://raw.githubusercontent.com/argoproj/argo-cd/refs/tags/v3.5.6/manifests/install.yaml
- certificate.yaml
- httproute.yaml
- oidc-secret.yaml
patches:
@@ -18,4 +19,7 @@ patches:
name: argocd-notifications-controller
path: overlays/argocd-notifications-controller-patch.yaml
- path: overlays/argocd-cm.patch.yaml
- path: overlays/argocd-rbac-cm.patch.yaml
- path: overlays/argocd-rbac-cm.patch.yaml
- path: overlays/argocd-cmd-params-cm.patch.yaml
- path: overlays/patched-ca-bundle.patch.yaml
- path: overlays/resources.patch.yaml
+1 -1
View File
@@ -1,4 +1,4 @@
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: argocd-oidc-secret
-14
View File
@@ -1,14 +0,0 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-cm
labels:
app.kubernetes.io/name: argocd-cm
app.kubernetes.io/part-of: argocd
data:
# kustomize.buildOptions: "--enable-helm"
resource.exclusions: |
- apiGroups:
- "velero.io"
kinds:
- "Backup"
@@ -0,0 +1,11 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: argocd-cmd-params-cm
labels:
app.kubernetes.io/name: argocd-cmd-params-cm
app.kubernetes.io/part-of: argocd
data:
# TLS ends at the Gateway, so argocd-server serves plain HTTP. The Gateway
# API has no simple way to trust argocd-server's self-signed cert.
server.insecure: "true"
@@ -0,0 +1,112 @@
# Mount patched-ca-bundle (from ca-bundle/) over /etc/ssl/certs so git, helm
# and the Go binaries stop trusting the compromised eMudhra intermediates.
# The whole directory is replaced because OpenSSL and Go also read the
# per-root files next to ca-certificates.crt. Drop this once Argo CD ships a
# fixed image.
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-server
spec:
template:
spec:
containers:
- name: argocd-server
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-repo-server
spec:
template:
spec:
containers:
- name: argocd-repo-server
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: argocd-application-controller
spec:
template:
spec:
containers:
- name: argocd-application-controller
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-applicationset-controller
spec:
template:
spec:
containers:
- name: argocd-applicationset-controller
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-notifications-controller
spec:
template:
spec:
containers:
- name: argocd-notifications-controller
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-dex-server
spec:
template:
spec:
containers:
- name: dex
volumeMounts:
- name: patched-ca-bundle
mountPath: /etc/ssl/certs
readOnly: true
volumes:
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
+100
View File
@@ -0,0 +1,100 @@
# Requests from what the components used on 2026-10-25 (kubectl top every
# 5 minutes; highest value plus 10%). No limits until there are daytime
# numbers, see docs/roadmap.md.
apiVersion: apps/v1
kind: StatefulSet
metadata:
name: argocd-application-controller
spec:
template:
spec:
containers:
- name: argocd-application-controller
resources:
requests:
cpu: 150m
memory: 704Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-repo-server
spec:
template:
spec:
containers:
- name: argocd-repo-server
resources:
requests:
cpu: 100m
memory: 128Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-server
spec:
template:
spec:
containers:
- name: argocd-server
resources:
requests:
cpu: 10m
memory: 64Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-redis
spec:
template:
spec:
containers:
- name: redis
resources:
requests:
cpu: 20m
memory: 96Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-applicationset-controller
spec:
template:
spec:
containers:
- name: argocd-applicationset-controller
resources:
requests:
cpu: 10m
memory: 48Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-notifications-controller
spec:
template:
spec:
containers:
- name: argocd-notifications-controller
resources:
requests:
cpu: 10m
memory: 48Mi
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: argocd-dex-server
spec:
template:
spec:
containers:
- name: dex
resources:
requests:
cpu: 10m
memory: 32Mi
+1 -1
View File
@@ -1,4 +1,4 @@
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: webhook-es
+42 -3
View File
@@ -11,12 +11,46 @@ Authentik is deployed as the central identity provider, providing OIDC and LDAP
- `blueprint-ldap.yaml` — LDAP provider (base DN: `DC=ldap,DC=goauthentik,DC=io`)
- `blueprint-mail-oidc.yaml` — OAuth2/OIDC provider for Stalwart mail
- `blueprint-vault-oidc.yaml` — OIDC provider for Vault
- `blueprint-argocd-oidc.yaml` — OIDC provider for ArgoCD
- `blueprint-freshrss-oidc.yaml` — OIDC provider for FreshRSS
- `blueprint-actualbudget-proxy.yaml` — Proxy provider for Actual Budget
- `blueprint-longhorn-oidc.yaml` — OIDC provider for Longhorn (Envoy Gateway SecurityPolicy)
- `blueprint-scouting.yaml` — immich's login with Scouts Online, see docs/immich-scouts-online.md
- `blueprint-session-duration.yaml` — Session lifetime of the default authentication flow
- **NetworkPolicies** (`networkpolicy.yaml`) — the pods reach each other, DNS and the internet,
not the LAN or other namespaces; the worker and the database also reach the API server
## Session lifetime
Authentik ships the login stage of `default-authentication-flow` with
`session_duration: seconds=0`, i.e. the SSO session dies when the browser closes.
`blueprint-session-duration.yaml` raises this to 30 days for every app that uses
that flow (FreshRSS, ArgoCD, Vault, Actual Budget, mail).
The expiry is **absolute** — Authentik does not extend a session on activity. A
sliding window has to come from the application itself; FreshRSS does this via
`OIDC_SESSION_INACTIVITY_TIMEOUT` (see `freshrss/freshrss-deployment.yaml`), which
Apache mod_auth_openidc refreshes on every request.
## LDAP Outpost
The LDAP outpost exposes Authentik's user directory over LDAP. It is used by:
- **SOGo-mail** (in-cluster) — connects via `ak-outpost-ldap-outpost.authentik.svc.cluster.local:3389`
- **Stalwart** (NixOS, external) — connects via `ldap.rubenhensen.nl:389`
The LDAP outpost exposes Authentik's user directory over LDAP. It is used by
**Stalwart** (NixOS on node001), which connects via `ldap.rubenhensen.nl:389`.
The outpost itself talks to the server through `https://authentik.rubenhensen.nl/`.
Authentik's worker deploys the outpost and keeps its version equal to the
server's. After the upgrades to 2026.5 and 2026.8 it didn't follow on its
own; this rolls it over:
```bash
kubectl -n authentik exec deploy/authentik-worker -- ak shell -c '
from authentik.outposts.models import Outpost
from authentik.outposts.tasks import outpost_controller
outpost_controller.send(Outpost.objects.get(name="LDAP outpost").pk)'
```
Upgrades go one release at a time (2026.2 → 2026.5 → 2026.8); since 2026.8
authentik refuses to skip one.
### NodePort Service
@@ -71,3 +105,8 @@ microk8s config > ~/.kube/config
```
**Note:** This must be re-applied after MicroK8s upgrades or cert rotations, as MicroK8s may regenerate the CA without the extension. The fix needs to run on every node in the cluster.
Checked 2026-10-25: the CA from this fix (`CN=microk8s-ca`, 2026-03-21, valid
until 2036) still has the extension after the refreshes to 1.34, 1.35 and
1.36. Check with
`openssl x509 -in /var/snap/microk8s/current/certs/ca.crt -noout -ext keyUsage`.
@@ -38,3 +38,12 @@ data:
name: Actual Budget
provider: !KeyOf actualbudget-provider
meta_launch_url: https://ynab.rubenhensen.nl
# Only admins: Scouts Online members get accounts in this authentik
# too (for immich) and must not reach personal apps.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf actualbudget-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+9
View File
@@ -38,3 +38,12 @@ data:
name: ArgoCD
provider: !KeyOf argocd-provider
meta_launch_url: https://argocd.rubenhensen.nl
# Only admins: Scouts Online members get accounts in this authentik
# too (for immich) and must not reach personal apps.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf argocd-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+9
View File
@@ -40,3 +40,12 @@ data:
name: FreshRSS
provider: !KeyOf freshrss-provider
meta_launch_url: https://rss.rubenhensen.nl
# Only admins: Scouts Online members get accounts in this authentik
# too (for immich) and must not reach personal apps.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf freshrss-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+50
View File
@@ -0,0 +1,50 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: authentik-blueprint-longhorn
data:
longhorn-oidc.yaml: |
version: 1
metadata:
name: Longhorn OIDC
entries:
# Envoy Gateway does the login for Longhorn, which has no users of its
# own (see longhorn/httproute.yaml).
- model: authentik_providers_oauth2.oauth2provider
id: longhorn-provider
state: present
identifiers:
name: Longhorn
attrs:
name: Longhorn
authorization_flow: !Find [authentik_flows.flow, [slug, default-provider-authorization-implicit-consent]]
authentication_flow: !Find [authentik_flows.flow, [slug, default-authentication-flow]]
invalidation_flow: !Find [authentik_flows.flow, [slug, default-provider-invalidation-flow]]
client_type: confidential
client_id: longhorn
client_secret: !Env [LONGHORN_OIDC_CLIENT_SECRET, ""]
redirect_uris:
- matching_mode: strict
url: https://longhorn.rubenhensen.nl/oauth2/callback
signing_key: !Find [authentik_crypto.certificatekeypair, [name, "authentik Self-signed Certificate"]]
property_mappings:
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-openid]]
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-email]]
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-profile]]
- model: authentik_core.application
id: longhorn-app
state: present
identifiers:
slug: longhorn
attrs:
name: Longhorn
provider: !KeyOf longhorn-provider
meta_launch_url: https://longhorn.rubenhensen.nl
# Longhorn can delete volumes, so only admins get in.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf longhorn-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+9
View File
@@ -38,3 +38,12 @@ data:
name: Stalwart Mail
provider: !KeyOf stalwart-provider
meta_launch_url: https://mail.rubenhensen.nl
# Only admins: Scouts Online members get accounts in this authentik
# too (for immich) and must not reach personal apps.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf stalwart-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+289
View File
@@ -0,0 +1,289 @@
# Login for the Scouting MBG photos (immich on foto.scoutingmbg.nl).
# Mounted as a directory, unlike the other blueprints, so authentik picks up
# changes without a restart; secrets come from files in /secrets/scouting
# for the same reason (see apps/templates/authentik-helm.yaml).
apiVersion: v1
kind: ConfigMap
metadata:
name: authentik-blueprint-scouting
data:
immich-oidc.yaml: |
version: 1
metadata:
name: immich OIDC
entries:
# The source and the login flow below come from scouts-online.yaml.
- model: authentik_blueprints.metaapplyblueprint
attrs:
identifiers:
path: custom/scouting/scouts-online.yaml
required: true
# Filled by the Scouts Online source on every login: every member, and
# the members with an active Kaderlid role.
- model: authentik_core.group
id: mbg-leden
state: present
identifiers:
name: MBG leden
- model: authentik_core.group
id: mbg-kader
state: present
identifiers:
name: MBG kader
# immich syncs both claims on every login. A quota of 0 makes immich
# refuse uploads, -1 means unlimited.
- model: authentik_providers_oauth2.scopemapping
id: immich-scope
state: present
identifiers:
name: "immich: role and quota"
attrs:
name: "immich: role and quota"
scope_name: immich
description: Upload rights in the Scouting MBG photos
expression: |
admin = ak_is_group_member(request.user, name="authentik Admins")
uploader = admin or ak_is_group_member(request.user, name="MBG kader")
return {
"immich_role": "admin" if admin else "user",
"immich_quota": -1 if uploader else 0,
}
- model: authentik_providers_oauth2.oauth2provider
id: immich-provider
state: present
identifiers:
name: immich
attrs:
name: immich
authorization_flow: !Find [authentik_flows.flow, [slug, default-provider-authorization-implicit-consent]]
# Straight on to Scouts Online. Admins with a password log in at
# authentik first.
authentication_flow: !Find [authentik_flows.flow, [slug, scouts-online-login]]
invalidation_flow: !Find [authentik_flows.flow, [slug, default-provider-invalidation-flow]]
client_type: confidential
client_id: immich
client_secret: !File /secrets/scouting/immich-oidc-client-secret
redirect_uris:
- matching_mode: strict
url: https://foto.scoutingmbg.nl/auth/login
# "Link to OAuth" in immich's account settings
- matching_mode: strict
url: https://foto.scoutingmbg.nl/user-settings
- matching_mode: strict
url: app.immich:///oauth-callback
signing_key: !Find [authentik_crypto.certificatekeypair, [name, "authentik Self-signed Certificate"]]
property_mappings:
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-openid]]
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-email]]
- !Find [authentik_providers_oauth2.scopemapping, [managed, goauthentik.io/providers/oauth2/scope-profile]]
- !KeyOf immich-scope
- model: authentik_core.application
id: immich-app
state: present
identifiers:
slug: immich
attrs:
name: Scouting MBG foto's
provider: !KeyOf immich-provider
meta_launch_url: https://foto.scoutingmbg.nl
policy_engine_mode: any
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf immich-app
attrs:
group: !KeyOf mbg-leden
# auth.scoutingmbg.nl: straight to Scouts Online, then on to the
# photos. Other domains keep the default brand.
- model: authentik_brands.brand
state: present
identifiers:
domain: auth.scoutingmbg.nl
attrs:
branding_title: Scouting MBG
flow_authentication: !Find [authentik_flows.flow, [slug, scouts-online-login]]
default_application: !KeyOf immich-app
- model: authentik_policies.policybinding
state: present
identifiers:
order: 1
target: !KeyOf immich-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
scouts-online.yaml: |
version: 1
metadata:
name: Scouts Online
entries:
- model: authentik_sources_oauth.oauthsourcepropertymapping
id: user-mapping
state: present
identifiers:
name: "Scouts Online: user"
attrs:
name: "Scouts Online: user"
expression: |
# info is the userinfo of Scouts Online (https://login.scouting.nl/docs/api).
# It only holds the roles within the organisations of this connection,
# which is just the group.
from datetime import date
today = date.today().isoformat()
roles = {role.get("id"): role for role in (info.get("roles") or {}).values()}
kader = False
for assignment in info.get("role_assignments") or []:
start = (assignment.get("start_date") or "")[:10]
end = (assignment.get("end_date") or "")[:10]
if (start and start > today) or (end and end < today):
continue
role = roles.get(assignment.get("role_id")) or {}
if "Kaderlid" in (role.get("member_type") or []):
kader = True
member_id = info.get("member_id")
email = info.get("email") or ""
# Family members can share an email address; immich needs one per account.
if email and info.get("multiple_accounts"):
local, _, domain = email.partition("@")
email = f"{local}+{member_id}@{domain}"
return {
"username": f"sol-{member_id}",
"email": email,
"name": info.get("name") or "",
"groups": ["MBG leden", "MBG kader"] if kader else ["MBG leden"],
"attributes": {"sol_member_id": member_id},
}
# The source's flows can only be reached through the source.
- model: authentik_policies_expression.expressionpolicy
id: sso-only
state: present
identifiers:
name: scouts-online-sso-only
attrs:
expression: return ak_is_sso_flow
# New members become external users: they can use the apps they are
# let into, not authentik's own interface.
- model: authentik_stages_user_write.userwritestage
id: user-write
state: present
identifiers:
name: scouts-online-user-write
attrs:
user_creation_mode: always_create
user_type: external
- model: authentik_stages_user_login.userloginstage
id: user-login
state: present
identifiers:
name: scouts-online-user-login
- model: authentik_flows.flow
id: enrollment-flow
state: present
identifiers:
slug: scouts-online-enrollment
attrs:
name: Scouts Online enrollment
title: Scouting MBG
designation: enrollment
authentication: none
- model: authentik_flows.flowstagebinding
state: present
identifiers:
order: 0
target: !KeyOf enrollment-flow
stage: !KeyOf user-write
- model: authentik_flows.flowstagebinding
state: present
identifiers:
order: 1
target: !KeyOf enrollment-flow
stage: !KeyOf user-login
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf enrollment-flow
policy: !KeyOf sso-only
- model: authentik_flows.flow
id: authentication-flow
state: present
identifiers:
slug: scouts-online-authentication
attrs:
name: Scouts Online authentication
title: Scouting MBG
designation: authentication
authentication: none
- model: authentik_flows.flowstagebinding
state: present
identifiers:
order: 0
target: !KeyOf authentication-flow
stage: !KeyOf user-login
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf authentication-flow
policy: !KeyOf sso-only
# SOL only lets in members of the organisations picked in its
# connection, and only sends roles within them. The callback URL is
# https://auth.scoutingmbg.nl/source/oauth/callback/scouts-online/ (and
# authentik.rubenhensen.nl, from before auth.scoutingmbg.nl existed)
- model: authentik_sources_oauth.oauthsource
id: source
state: present
identifiers:
slug: scouts-online
attrs:
name: Scouts Online
slug: scouts-online
enabled: true
provider_type: openidconnect
consumer_key: !File /secrets/scouting/scouts-online-client-id
consumer_secret: !File /secrets/scouting/scouts-online-client-secret
authorization_url: https://login.scouting.nl/authorize
access_token_url: https://login.scouting.nl/token
profile_url: https://login.scouting.nl/oidc/userinfo
oidc_well_known_url: https://login.scouting.nl/.well-known/openid-configuration
oidc_jwks_url: https://login.scouting.nl/.well-known/openid-jwks.json
additional_scopes: membership roles
pkce: S256
authorization_code_auth_method: basic_auth
user_matching_mode: identifier
# Links to the groups that immich-oidc.yaml creates
group_matching_mode: name_link
user_path_template: goauthentik.io/sources/scouts-online
enrollment_flow: !KeyOf enrollment-flow
authentication_flow: !KeyOf authentication-flow
user_property_mappings:
- !KeyOf user-mapping
# Where immich sends people who aren't logged in. An identification
# stage without fields and with one source goes straight to it.
- model: authentik_stages_identification.identificationstage
id: identification
state: present
identifiers:
name: scouts-online-identification
attrs:
user_fields: []
sources:
- !KeyOf source
show_source_labels: true
- model: authentik_flows.flow
id: login-flow
state: present
identifiers:
slug: scouts-online-login
attrs:
name: Scouts Online login
title: Scouting MBG
designation: authentication
- model: authentik_flows.flowstagebinding
state: present
identifiers:
order: 0
target: !KeyOf login-flow
stage: !KeyOf identification
+27
View File
@@ -0,0 +1,27 @@
apiVersion: v1
kind: ConfigMap
metadata:
name: authentik-blueprint-session
data:
session-duration.yaml: |
version: 1
metadata:
name: Session duration
entries:
# Overrides the login stage of the built-in `default-authentication-flow`,
# which every OIDC/proxy provider in this cluster authenticates against.
# authentik ships this stage with `session_duration: seconds=0`, which means
# "until the browser is closed" — that is why re-logins were so frequent.
#
# Note: authentik's session expiry is absolute (counted from login), it does
# not slide on activity. The sliding window lives in the applications, e.g.
# OIDC_SESSION_INACTIVITY_TIMEOUT in freshrss/freshrss-deployment.yaml.
- model: authentik_stages_user_login.userloginstage
state: present
identifiers:
name: default-authentication-login
attrs:
session_duration: days=30
# Uncomment to show a "Remember me on this device" checkbox that adds
# this offset on top of session_duration when ticked (0 = hidden).
# remember_me_offset: days=60
+9
View File
@@ -40,3 +40,12 @@ data:
name: Vault
provider: !KeyOf vault-provider
meta_launch_url: https://vault.rubenhensen.nl
# Only admins: Scouts Online members get accounts in this authentik
# too (for immich) and must not reach personal apps.
- model: authentik_policies.policybinding
state: present
identifiers:
order: 0
target: !KeyOf vault-app
attrs:
group: !Find [authentik_core.group, [name, "authentik Admins"]]
+33
View File
@@ -0,0 +1,33 @@
# The TLS certificate the Gateway serves for this app (see httproute.yaml).
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: authentik-tls
spec:
secretName: authentik-tls
dnsNames:
- authentik.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
---
# The login of the Scouting MBG photos (immich), see blueprint-scouting.yaml.
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: auth-scoutingmbg-tls
spec:
secretName: auth-scoutingmbg-tls
dnsNames:
- auth.scoutingmbg.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
+68 -7
View File
@@ -1,4 +1,4 @@
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: authentik-secrets
@@ -24,7 +24,7 @@ spec:
key: kv/authentik
property: bootstrap_token
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: authentik-postgres-credentials
@@ -46,7 +46,7 @@ spec:
key: kv/authentik
property: postgres_password
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: vault-oidc-client-secret
@@ -64,7 +64,7 @@ spec:
key: kv/vault-oidc
property: client_secret
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: stalwart-oidc-client-secret
@@ -82,7 +82,7 @@ spec:
key: kv/stalwart-oidc
property: client_secret
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: argocd-oidc-client-secret
@@ -100,7 +100,7 @@ spec:
key: kv/argocd-oidc
property: client_secret
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: freshrss-oidc-client-secret
@@ -118,7 +118,7 @@ spec:
key: kv/freshrss-oidc
property: client_secret
---
apiVersion: external-secrets.io/v1beta1
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: actualbudget-oidc-client-secret
@@ -135,3 +135,64 @@ spec:
remoteRef:
key: kv/actualbudget-oidc
property: client_secret
---
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: longhorn-oidc-client-secret
spec:
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
refreshInterval: 15m
target:
name: longhorn-oidc-client-secret
creationPolicy: Owner
data:
- secretKey: client_secret
remoteRef:
key: kv/longhorn-oidc
property: client_secret
---
# Mounted as a file for blueprint-scouting.yaml, not as an env variable.
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: immich-oidc-client-secret
spec:
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
refreshInterval: 15m
target:
name: immich-oidc-client-secret
creationPolicy: Owner
data:
- secretKey: client_secret
remoteRef:
key: kv/immich-oidc
property: client_secret
---
# The Scouts Online connection (login.scouting.nl, "Beheerde websites"),
# mounted as files for blueprint-scouting.yaml.
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: scouts-online-client
spec:
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
refreshInterval: 15m
target:
name: scouts-online-client
creationPolicy: Owner
data:
- secretKey: client_id
remoteRef:
key: kv/scouts-online
property: client_id
- secretKey: client_secret
remoteRef:
key: kv/scouts-online
property: client_secret
+41
View File
@@ -0,0 +1,41 @@
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: authentik
spec:
parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: https-authentik
- name: homelab
namespace: envoy-gateway-system
sectionName: https-auth-scoutingmbg
hostnames:
- authentik.rubenhensen.nl
- auth.scoutingmbg.nl
rules:
- backendRefs:
- name: authentik-server
port: 80
# No limit on the whole request, as with nginx. Envoy's default of 15s
# cuts off uploads and long-lived connections.
timeouts:
request: 0s
---
# Lets the Gateway serve the certificate cert-manager keeps in this namespace.
apiVersion: gateway.networking.k8s.io/v1
kind: ReferenceGrant
metadata:
name: gateway-tls
spec:
from:
- group: gateway.networking.k8s.io
kind: Gateway
namespace: envoy-gateway-system
to:
- group: ""
kind: Secret
name: authentik-tls
- group: ""
kind: Secret
name: auth-scoutingmbg-tls
+137
View File
@@ -0,0 +1,137 @@
# authentik faces the internet (the login for every member of the group),
# so its pods only reach each other, DNS and the internet: not the LAN
# (NAS, router) or other namespaces. Scouts Online, the apps' OIDC calls
# and the LDAP outpost's connection to the server all use public
# addresses. The worker and the CNPG instance manager also reach the API
# server (the node, port 16443). Ingress comes from Envoy, the CNPG
# operator, the node itself (kubelet probes; 10.1.7.64 is the node's
# Calico VXLAN address, projectcalico.org/IPv4VXLANTunnelAddr), and for
# the LDAP outpost from anywhere: Stalwart on node001 comes in through the
# router and the ldap-outpost-external NodePort.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default
spec:
podSelector: {}
policyTypes:
- Ingress
- Egress
ingress:
- from:
- podSelector: {}
- from:
- ipBlock:
cidr: 192.168.1.204/32
- ipBlock:
cidr: 10.1.7.64/32
egress:
- to:
- podSelector: {}
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: kube-dns
ports:
- protocol: UDP
port: 53
- protocol: TCP
port: 53
- to:
- ipBlock:
cidr: 0.0.0.0/0
except:
- 10.0.0.0/8
- 100.64.0.0/10
- 169.254.0.0/16
- 172.16.0.0/12
- 192.168.0.0/16
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: server-from-envoy
spec:
podSelector:
matchLabels:
app.kubernetes.io/name: authentik
app.kubernetes.io/component: server
policyTypes:
- Ingress
ingress:
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: envoy-gateway-system
podSelector:
matchLabels:
app.kubernetes.io/name: envoy
ports:
- port: 9000
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: ldap-outpost
spec:
podSelector:
matchLabels:
app.kubernetes.io/name: authentik-outpost-ldap
policyTypes:
- Ingress
ingress:
- ports:
- port: 3389
- port: 6636
---
# The outpost controller deploys and updates the LDAP outpost.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: worker-to-api
spec:
podSelector:
matchLabels:
app.kubernetes.io/name: authentik
app.kubernetes.io/component: worker
policyTypes:
- Egress
egress:
- to:
- ipBlock:
cidr: 192.168.1.204/32
ports:
- port: 16443
---
# The CNPG operator checks each instance on its status port and connects to
# PostgreSQL; the instance manager inside each pod watches its Cluster
# through the API server.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: postgres-cnpg
spec:
podSelector:
matchExpressions:
- key: cnpg.io/cluster
operator: Exists
policyTypes:
- Ingress
- Egress
ingress:
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: cnpg-system
ports:
- port: 8000
- port: 5432
egress:
- to:
- ipBlock:
cidr: 192.168.1.204/32
ports:
- port: 16443
+7
View File
@@ -4,7 +4,14 @@ metadata:
name: authentik-postgres
spec:
instances: 1
# Pinned so a new operator default (PostgreSQL 18 since CNPG 1.26.3) can't
# start an in-place major upgrade. CNPG filled this in at creation.
imageName: ghcr.io/cloudnative-pg/postgresql:17.4
primaryUpdateStrategy: unsupervised
resources:
requests:
cpu: 50m
memory: 256Mi
bootstrap:
initdb:
database: authentik
+14
View File
@@ -1,5 +1,19 @@
# Velero Backup Testing Guide
**Use `restore-test.sh`.** It restores a few namespaces from a real backup
into a throwaway k3s in Docker, from a read-only copy of the bucket, and
checks that every volume comes back with the bytes it was backed up with:
```bash
backup-testing/restore-test.sh # newest daily backup; ntfy, freshrss, actual-budget
backup-testing/restore-test.sh <backup> <namespace>... # something else
```
How it works and why it copies instead of pointing Velero at the NAS is at
the top of the script. The rest of this README describes the older k3d
scripts, which predate Envoy Gateway and still expect `*.hensen.io` and
sol-auth.
This guide explains how to test your Velero backups using a temporary K3d cluster.
## Features
+222
View File
@@ -0,0 +1,222 @@
#!/bin/bash
# Restore a few namespaces from the real Velero backups into a throwaway
# k3s in Docker, to prove the backups can be restored. Nothing on the NAS
# changes:
# - one backup (backups/<name>/) and the kopia repositories of the chosen
# namespaces (kopia/<namespace>/) are copied read-only from the NAS with
# rclone into a Docker volume. A second Velero on the real bucket could
# run kopia maintenance on the same repositories as the cluster's own
# - `rclone serve s3` serves that copy to a Velero 1.18.2 in k3s, with a
# ReadOnly backup storage location
# - storage class longhorn becomes local-path; only core workload
# resources are restored (no routes, certificates, ExternalSecrets or
# NetworkPolicies)
# - every pod volume restore has to complete with as many bytes as its
# backup had, and the restored deployments have to become available
#
# Usage (on a machine with docker, kubectl and jq):
# backup-testing/restore-test.sh [backup] [namespace ...]
# Defaults: the newest Completed daily-backup, and ntfy freshrss
# actual-budget. Not gatus: a restored Gatus would start sending alerts.
#
# It reads Velero's S3 key from the cluster (velero/velero-s3-credentials)
# into a temporary directory, and the copied backup holds every Secret of
# the cluster; all of it is deleted at the end. KEEP=1 keeps the test
# cluster (kubeconfig in the printed directory) until you run it with
# CLEANUP=1. FROM_VOLUME=<docker volume> takes the bucket from a volume
# instead of the NAS (for rehearsals; laid out as <bucket>/backups/...).
#
# Rehearsed on 2026-10-25 against a backup made in the test cluster itself,
# which is how two pitfalls showed up: Velero skips hostPath volumes, and
# k3s only provisions local PVs (which it can back up and restore) for a
# storage class with the annotation defaultVolumeType: local.
set -euo pipefail
PROD_KUBECONFIG=${PROD_KUBECONFIG:-$HOME/.kube/homelab-config}
PORT=${PORT:-16443}
K3S=rancher/k3s:v1.34.9-k3s1
RCLONE=rclone/rclone:1.75.1
HELM=alpine/helm:3.19.0
VELERO_CHART=12.2.1
AWS_PLUGIN=velero/velero-plugin-for-aws:v1.14.4
NET=restore-test VOL=restore-test-s3
cleanup() {
docker rm -f -v restore-k3s restore-s3 >/dev/null 2>&1 || true
docker volume rm "$VOL" >/dev/null 2>&1 || true
docker network rm "$NET" >/dev/null 2>&1 || true
[[ -n ${WORK:-} ]] && rm -rf "$WORK"
}
if [[ ${CLEANUP:-} == 1 ]]; then
cleanup; rm -rf "${TMPDIR:-/tmp}"/restore-test.*; echo "cleaned up"; exit 0
fi
if docker ps -a --format '{{.Names}}' | grep -qx restore-k3s; then
echo "A test cluster from an earlier run exists; run with CLEANUP=1 first." >&2
exit 1
fi
WORK=$(mktemp -d "${TMPDIR:-/tmp}/restore-test.XXXXXX")
chmod 700 "$WORK"
[[ ${KEEP:-} == 1 ]] || trap cleanup EXIT
pk() { kubectl --kubeconfig "$PROD_KUBECONFIG" "$@"; }
tk() { kubectl --kubeconfig "$WORK/kubeconfig" "$@"; }
# wait_for <seconds> <what> <command...>
wait_for() {
local limit=$1 what=$2; shift 2
local end=$((SECONDS + limit))
until "$@" >/dev/null 2>&1; do
if ((SECONDS > end)); then echo "timed out waiting for $what" >&2; exit 1; fi
sleep 5
done
}
# Endpoint, region and bucket as Velero itself uses them. The NAS rejects a
# request signed for the wrong region (rclone defaults to us-east-1); MinIO
# did so with a bare 400 on HEAD.
if [[ -n ${FROM_VOLUME:-} ]]; then
BUCKET=${BUCKET:-velero-backups}
else
bsl=$(pk -n velero get backupstoragelocations default -o json)
S3URL=${S3URL:-$(jq -r '.spec.config.s3Url' <<<"$bsl")}
REGION=${REGION:-$(jq -r '.spec.config.region // "us-east-1"' <<<"$bsl")}
BUCKET=${BUCKET:-$(jq -r '.spec.objectStorage.bucket' <<<"$bsl")}
fi
backup=${1:-}
shift || true
namespaces=("$@")
[[ ${#namespaces[@]} -gt 0 ]] || namespaces=(ntfy freshrss actual-budget)
if [[ -z $backup ]]; then
backup=$(pk -n velero get backups.velero.io -o json | jq -r '[.items[]
| select(.metadata.labels["velero.io/schedule-name"] == "daily-backup" and .status.phase == "Completed")]
| max_by(.status.startTimestamp).metadata.name')
fi
echo "== backup $backup, namespaces: ${namespaces[*]}"
docker network create "$NET" >/dev/null
docker volume create "$VOL" >/dev/null
if [[ -n ${FROM_VOLUME:-} ]]; then
echo "== copy from the volume $FROM_VOLUME"
docker run --rm -v "$FROM_VOLUME:/from:ro" -v "$VOL:/data" alpine:3.22 cp -a /from/. /data/
else
echo "== copy from the NAS (read-only)"
(umask 077; pk -n velero get secret velero-s3-credentials -o jsonpath='{.data.cloud}' | base64 -d |
awk -F' *= *' '/aws_access_key_id/ {print "RCLONE_CONFIG_NAS_ACCESS_KEY_ID="$2}
/aws_secret_access_key/ {print "RCLONE_CONFIG_NAS_SECRET_ACCESS_KEY="$2}' > "$WORK/nas.env"
printf 'RCLONE_CONFIG_NAS_TYPE=s3\nRCLONE_CONFIG_NAS_PROVIDER=Other\nRCLONE_CONFIG_NAS_ENDPOINT=%s\nRCLONE_CONFIG_NAS_REGION=%s\n' "$S3URL" "$REGION" >> "$WORK/nas.env")
copy() { docker run --rm --env-file "$WORK/nas.env" -v "$VOL:/data" "$RCLONE" copy --stats-one-line "nas:$BUCKET/$1" "/data/$BUCKET/$1"; }
copy "backups/$backup"
for ns in "${namespaces[@]}"; do copy "kopia/$ns"; done
rm -f "$WORK/nas.env"
fi
echo "== local S3 and k3s"
docker run -d --name restore-s3 --network "$NET" -v "$VOL:/data" "$RCLONE" \
serve s3 /data --addr :8080 --auth-key test,restore-test-secret >/dev/null
s3ip=$(docker inspect -f "{{(index .NetworkSettings.Networks \"$NET\").IPAddress}}" restore-s3)
docker run -d --name restore-k3s --privileged --network "$NET" -p "127.0.0.1:$PORT:6443" "$K3S" \
server --disable traefik --disable metrics-server --tls-san 127.0.0.1 --tls-san restore-k3s >/dev/null
node_ready() { docker exec restore-k3s kubectl get nodes 2>/dev/null | grep -q ' Ready'; }
wait_for 180 "k3s" node_ready
docker exec restore-k3s cat /etc/rancher/k3s/k3s.yaml | sed "s#https://127.0.0.1:6443#https://127.0.0.1:$PORT#" > "$WORK/kubeconfig"
docker exec restore-k3s cat /etc/rancher/k3s/k3s.yaml | sed 's#https://127.0.0.1:6443#https://restore-k3s:6443#' > "$WORK/kubeconfig-net"
echo "== Velero"
cat > "$WORK/values.yaml" <<EOF
configuration:
backupStorageLocation:
- name: default
provider: aws
bucket: $BUCKET
accessMode: ReadOnly
config:
region: minio
s3ForcePathStyle: "true"
s3Url: http://$s3ip:8080
volumeSnapshotLocation: []
defaultRepoMaintainFrequency: 8760h
credentials:
secretContents:
cloud: |
[default]
aws_access_key_id=test
aws_secret_access_key=restore-test-secret
initContainers:
- name: velero-plugin-for-aws
image: $AWS_PLUGIN
volumeMounts:
- mountPath: /target
name: plugins
deployNodeAgent: true
snapshotsEnabled: false
upgradeCRDs: false
EOF
docker run --rm --network "$NET" -e HOME=/tmp -e KC="$(base64 < "$WORK/kubeconfig-net")" \
-e VALUES="$(base64 < "$WORK/values.yaml")" --entrypoint sh "$HELM" -c '
echo "$KC" | base64 -d > /tmp/kc && echo "$VALUES" | base64 -d > /tmp/v.yaml &&
helm --kubeconfig /tmp/kc install velero velero --repo https://vmware-tanzu.github.io/helm-charts \
--version '"$VELERO_CHART"' -n velero --create-namespace -f /tmp/v.yaml >/dev/null'
tk apply -f - >/dev/null <<EOF
apiVersion: v1
kind: ConfigMap
metadata:
name: change-storage-class
namespace: velero
labels:
velero.io/plugin-config: ""
velero.io/change-storage-class: RestoreItemAction
data:
longhorn: local-path
EOF
wait_for 300 "Velero to sync $backup" tk -n velero get backups.velero.io "$backup"
echo " Velero sees $backup"
echo "== restore"
tk apply -f - >/dev/null <<EOF
apiVersion: velero.io/v1
kind: Restore
metadata:
name: restore-test
namespace: velero
spec:
backupName: $backup
includedNamespaces: [$(IFS=,; echo "${namespaces[*]}")]
# PersistentVolumes have to be included: only then does Velero clear the
# PVC's volumeName. It doesn't restore a PV whose data comes from kopia;
# k3s provisions a new one.
includedResources: [namespaces, persistentvolumeclaims, persistentvolumes, pods, deployments,
replicasets, statefulsets, services, configmaps, secrets, serviceaccounts]
restorePVs: true
EOF
restore_done() { [[ $(tk -n velero get restore restore-test -o jsonpath='{.status.phase}') =~ ^(Completed|PartiallyFailed|Failed|FailedValidation)$ ]]; }
wait_for 1800 "the restore" restore_done
phase=$(tk -n velero get restore restore-test -o jsonpath='{.status.phase}')
echo " restore: $phase"
echo "== check"
failed=0
expected=$(docker run --rm -v "$VOL:/data" alpine:3.22 zcat "/data/$BUCKET/backups/$backup/$backup-podvolumebackups.json.gz" |
jq -r --arg ns "$(IFS=,; echo "${namespaces[*]}")" '.[] | select(.spec.pod.namespace as $p | $ns | split(",") | index($p))
| "\(.spec.pod.namespace)/\(.spec.volume) \(.status.progress.totalBytes // 0)"' | sort -u)
restored=$(tk -n velero get podvolumerestores.velero.io -o json |
jq -r '.items[] | "\(.spec.pod.namespace)/\(.spec.volume) \(.status.progress.totalBytes // 0) \(.status.phase)"' | sort -u)
while read -r vol bytes; do
[[ -z $vol ]] && continue
got=$(awk -v v="$vol" '$1 == v {print $2, $3}' <<<"$restored")
if [[ $got == "$bytes Completed" ]]; then
echo " ok $vol ($bytes bytes)"
else
echo " FAILED $vol: backed up $bytes bytes, restore: ${got:-none}"; failed=1
fi
done <<<"$expected"
for ns in "${namespaces[@]}"; do
if tk -n "$ns" wait --for=condition=Available deployment --all --timeout=300s >/dev/null 2>&1; then
echo " ok $ns: deployments available"
else
echo " FAILED $ns: deployments not available"; tk -n "$ns" get pods; failed=1
fi
done
[[ $phase == Completed ]] || failed=1
[[ ${KEEP:-} == 1 ]] && echo "Kept; kubeconfig: $WORK/kubeconfig. Remove with CLEANUP=1 $0"
if [[ $failed == 0 ]]; then echo "== restore test passed"; else echo "== restore test FAILED"; exit 1; fi
-381
View File
@@ -1,381 +0,0 @@
#!/bin/bash
# test-velero-backup.sh - Automated script to test Velero backups
set -e
# Configuration - customize these variables
BACKUP_NAME="" # Will list backups if empty
S3_BUCKET="velero-backups"
S3_REGION="minio"
S3_URL="http://192.168.1.99:9000" # Your NAS MinIO server
S3_ACCESS_KEY="" # Will be filled from credentials
S3_SECRET_KEY="" # Will be filled from credentials
ORIGINAL_NAMESPACE="" # Namespace in the original backup
TEST_NAMESPACE="default"
DEBUG=false # Set to true for verbose debugging
# Parse command line arguments
while [[ $# -gt 0 ]]; do
case $1 in
--backup-name)
BACKUP_NAME="$2"
shift 2
;;
--s3-access-key)
S3_ACCESS_KEY="$2"
shift 2
;;
--s3-secret-key)
S3_SECRET_KEY="$2"
shift 2
;;
--s3-bucket)
S3_BUCKET="$2"
shift 2
;;
--s3-region)
S3_REGION="$2"
shift 2
;;
--s3-url)
S3_URL="$2"
shift 2
;;
--original-namespace)
ORIGINAL_NAMESPACE="$2"
shift 2
;;
--test-namespace)
TEST_NAMESPACE="$2"
shift 2
;;
--debug)
DEBUG=true
shift
;;
--help)
echo "Usage: $0 [options]"
echo "Options:"
echo " --backup-name NAME Name of the Velero backup to restore"
echo " --s3-bucket BUCKET S3 bucket containing backups"
echo " --s3-region REGION S3 region"
echo " --s3-url URL S3 endpoint URL"
echo " --s3-access-key KEY S3 access key"
echo " --s3-secret-key KEY S3 secret key"
echo " --original-namespace NS Namespace in the original backup"
echo " --test-namespace NS Namespace for restoration (default: default)"
echo " --debug Enable debug output"
echo " --help Show this help message"
exit 0
;;
*)
echo "Unknown option: $1"
exit 1
;;
esac
done
# Verify required variables
if [[ -z "$S3_BUCKET" || -z "$S3_REGION" || -z "$S3_ACCESS_KEY" || -z "$S3_SECRET_KEY" || -z "$ORIGINAL_NAMESPACE" || -z "$TEST_NAMESPACE" ]]; then
echo "Error: S3 configuration is incomplete"
exit 1
fi
# Function to clean up resources
cleanup() {
echo "Cleaning up resources..."
k3d cluster delete backup-test || true
echo "Cleanup complete"
}
# Function for debugging output
debug() {
if [[ "$DEBUG" == "true" ]]; then
echo "[DEBUG] $*"
fi
}
# Register cleanup function to run on exit (ctrl+c, etc.)
trap cleanup EXIT
echo "=== Starting Velero backup test process ==="
# 1. Create K3d cluster
echo "Creating K3d cluster..."
k3d cluster create backup-test \
--api-port 6443 \
--port "80:80@loadbalancer" \
--port "443:443@loadbalancer" \
--agents 0 \
--k3s-arg "--disable=traefik@server:0" \
--wait
# -v /mnt/longhorn:/var/lib/longhorn:shared@all \
# -i hebury/k3s:v1.32.2-k3s1 \
# --wait
# Verify cluster is running
kubectl config use-context k3d-backup-test
kubectl get nodes
# 2. Install Longhorn
# echo "Installing Longhorn..."
# kubectl create namespace longhorn-system
# helm repo add longhorn https://charts.longhorn.io
# helm repo update
# helm install longhorn longhorn/longhorn \
# --namespace longhorn-system \
# --set persistence.defaultClassReplicaCount=1 \
# --set defaultSettings.backupTarget="" \
# --set defaultSettings.defaultReplicaCount=1
# echo "Waiting for Longhorn to be ready..."
# kubectl -n longhorn-system rollout status deployment/longhorn-ui
# kubectl -n longhorn-system rollout status deployment/longhorn-driver-deployer
# kubectl -n longhorn-system rollout status daemonset/longhorn-manager
# 3. Install Velero with S3 provider
echo "Installing Velero..."
cat > velero-credentials <<EOF
[default]
aws_access_key_id=$S3_ACCESS_KEY
aws_secret_access_key=$S3_SECRET_KEY
EOF
helm repo add vmware-tanzu https://vmware-tanzu.github.io/helm-charts
helm repo update
debug "Installing Velero with S3 configuration:"
debug " Bucket: $S3_BUCKET"
debug " Region: $S3_REGION"
debug " URL: $S3_URL"
helm install velero vmware-tanzu/velero \
--namespace velero \
--create-namespace \
--set-file credentials.secretContents.cloud=velero-credentials \
--set configuration.backupStorageLocation[0].provider=aws \
--set configuration.backupStorageLocation[0].name=default \
--set configuration.backupStorageLocation[0].bucket=$S3_BUCKET \
--set configuration.backupStorageLocation[0].config.region=$S3_REGION \
--set configuration.backupStorageLocation[0].config.s3ForcePathStyle=true \
--set configuration.backupStorageLocation[0].config.s3Url=$S3_URL \
--set configuration.volumeSnapshotLocation[0].name=default \
--set configuration.volumeSnapshotLocation[0].provider=aws \
--set configuration.volumeSnapshotLocation[0].config.region=$S3_REGION \
--set configuration.features=EnableCSI \
--set initContainers[0].name=velero-plugin-for-aws \
--set initContainers[0].image=velero/velero-plugin-for-aws:v1.11.1 \
--set initContainers[0].volumeMounts[0].mountPath=/target \
--set initContainers[0].volumeMounts[0].name=plugins \
--set deployNodeAgent=true \
--set nodeAgent.containerSecurityContext.privileged=true \
--wait
rm velero-credentials
# Wait for Velero to be ready
echo "Waiting for Velero to be fully ready..."
kubectl -n velero rollout status deployment/velero --timeout=120s
echo "Install change-storage-class.yaml"
kubectl apply -f change-storage-class.yaml
# Check if velero CLI is installed and functioning
if ! command -v velero &> /dev/null; then
echo "Error: Velero CLI is not installed or not in PATH"
echo "Please install the Velero CLI by following instructions at: https://velero.io/docs/main/basic-install/"
exit 1
fi
# Verify Velero is connected to the storage location
echo "Checking Velero backup storage location..."
kubectl -n velero get backupstoragelocation default -o jsonpath='{.status.phase}' | grep -q "Available" || {
echo "Warning: Backup storage location is not available, it may take a few minutes to initialize"
echo "Storage location status:"
kubectl -n velero get backupstoragelocation default -o yaml
# Wait a bit longer for the location to become available
echo "Waiting 30 seconds for backup storage location to become available..."
sleep 30
}
# 4. List backups
echo "Checking for available backups..."
if ! velero_output=$(velero backup get 2>&1); then
echo "Error listing backups: $velero_output"
# Try to verify S3 connectivity
echo "Checking S3 connectivity..."
# Install AWS CLI if needed
if ! command -v aws &> /dev/null; then
echo "AWS CLI not found, skipping S3 connectivity test"
else
# Create temporary AWS profile
mkdir -p ~/.aws
cat > ~/.aws/credentials <<EOF
[velero-test]
aws_access_key_id=$S3_ACCESS_KEY
aws_secret_access_key=$S3_SECRET_KEY
EOF
cat > ~/.aws/config <<EOF
[profile velero-test]
region=$S3_REGION
output=json
EOF
# Try to list bucket contents
echo "Testing S3 connection to bucket $S3_BUCKET..."
if aws --profile velero-test --endpoint-url $S3_URL s3 ls s3://$S3_BUCKET/; then
echo "S3 connection successful, but Velero couldn't list backups."
echo "This might indicate that there are no backups in the bucket or the backups are in a different format than expected."
else
echo "Error connecting to S3. Please check your credentials and connectivity to $S3_URL"
fi
# Cleanup AWS files
rm ~/.aws/credentials ~/.aws/config
fi
if [[ -z "$BACKUP_NAME" ]]; then
echo "No backup name specified and no backups found. Exiting."
exit 1
fi
else
echo "Available backups:"
echo "$velero_output"
if [[ -z "$BACKUP_NAME" ]]; then
echo "Specify a backup name using --backup-name and run again."
exit 0
fi
fi
# 5. Create test namespace if needed
if [[ "$TEST_NAMESPACE" != "default" ]]; then
kubectl create namespace $TEST_NAMESPACE || true
fi
# 6. Restore backup
echo "Restoring backup: $BACKUP_NAME"
if [[ -z "$ORIGINAL_NAMESPACE" ]]; then
# If no namespace specified, restore everything
velero restore create --from-backup $BACKUP_NAME \
--wait
else
# Restore specific namespace with mapping
velero restore create --from-backup $BACKUP_NAME \
--namespace-mappings $ORIGINAL_NAMESPACE:$TEST_NAMESPACE \
--include-namespaces $ORIGINAL_NAMESPACE \
--exclude-namespaces kube-system,kube-public,kube-node-lease,velero \
--exclude-resources certificates.cert-manager.io \
--wait
fi
# 7. Check restore status
echo "Checking restore status:"
velero restore get
# Wait for pods to be ready
echo "Waiting for pods to be ready..."
kubectl wait --for=condition=ready pod --all -n $TEST_NAMESPACE --timeout=600s || true
# 8. Run validation script (create it first if it doesn't exist)
# if [[ ! -f ./validate-restore.sh ]]; then
# echo "Creating validation script..."
# cat > validate-restore.sh <<'EOF'
# #!/bin/bash
# # validate-restore.sh - Script to validate Velero backup restoration
# set -e
# echo "Starting validation of restored resources..."
# # Get namespace from command line or use default
# NAMESPACE="${1:-default}"
# # Check all deployments
# echo "Checking deployments..."
# deployments=$(kubectl get deployment -n $NAMESPACE -o name)
# if [[ -z "$deployments" ]]; then
# echo "❌ No deployments found in namespace $NAMESPACE"
# else
# echo "Found deployments: $deployments"
# # Check if pods are running for each deployment
# for deployment in $deployments; do
# name=$(echo $deployment | cut -d'/' -f2)
# echo -n "Checking deployment $name: "
# # Check if pods are running
# ready_replicas=$(kubectl get deployment -n $NAMESPACE $name -o jsonpath='{.status.readyReplicas}')
# if [[ -n "$ready_replicas" && "$ready_replicas" != "0" ]]; then
# echo "✅ $ready_replicas pods ready"
# else
# echo "❌ No pods running"
# fi
# done
# fi
# # Check all services
# echo "Checking services..."
# services=$(kubectl get service -n $NAMESPACE -o name | grep -v "kubernetes")
# if [[ -z "$services" ]]; then
# echo "❌ No services found in namespace $NAMESPACE"
# else
# echo "Found services: $services"
# # Check if services have endpoints
# for service in $services; do
# name=$(echo $service | cut -d'/' -f2)
# echo -n "Checking service $name: "
# # Check if service has endpoints
# endpoints=$(kubectl get endpoints -n $NAMESPACE $name -o jsonpath='{.subsets[*].addresses[*].ip}')
# if [ -n "$endpoints" ]; then
# echo "✅ Has endpoints"
# else
# echo "❌ No endpoints"
# fi
# done
# fi
# # Check PVCs
# echo "Checking PVCs..."
# pvcs=$(kubectl get pvc -n $NAMESPACE -o name)
# if [[ -z "$pvcs" ]]; then
# echo "No PVCs found in namespace $NAMESPACE"
# else
# pvc_count=$(echo "$pvcs" | wc -l)
# echo "Found $pvc_count PVCs"
# # Check if PVCs are bound
# bound_count=$(kubectl get pvc -n $NAMESPACE -o jsonpath='{.items[?(@.status.phase=="Bound")].metadata.name}' | wc -w)
# echo "$bound_count/$pvc_count PVCs are bound"
# if [ "$bound_count" -ne "$pvc_count" ]; then
# echo "❌ Not all PVCs are bound"
# else
# echo "✅ All PVCs are bound"
# fi
# fi
# echo "Validation complete!"
# exit 0
# EOF
# chmod +x validate-restore.sh
# fi
echo "Running validation tests..."
./validate-restore.sh $TEST_NAMESPACE
echo ""
echo "=== Backup test process completed ==="
echo "The cluster will be deleted when you close this terminal or press Ctrl+C"
echo "To access the cluster manually, use: kubectl config use-context k3d-backup-test"
echo ""
# Keep the script running until user terminates it
read -p "Press Enter to clean up and exit..."
+111
View File
@@ -0,0 +1,111 @@
apiVersion: apps/v1
kind: Deployment
metadata:
labels:
app: bolletjestrui
name: bolletjestrui
spec:
replicas: 1
selector:
matchLabels:
app: bolletjestrui
strategy:
type: Recreate
template:
metadata:
labels:
app: bolletjestrui
spec:
containers:
- image: ghcr.io/rubenhensen/bolletjestrui:main-10268f1
name: bolletjestrui
ports:
- containerPort: 3000
protocol: TCP
env:
- name: DATABASE_URL
value: /app/data/bolletjestrui.db
- name: ORIGIN
value: https://vic.rubenhensen.nl
- name: PROTOCOL_HEADER
value: x-forwarded-proto
- name: HOST_HEADER
value: x-forwarded-host
# GPX routes and profile photos (up to 20 MB); raise adapter-node's 512K default
- name: BODY_SIZE_LIMIT
value: "25M"
- name: TZ
value: Europe/Amsterdam
- name: SITE_PASSWORD
valueFrom:
secretKeyRef:
name: bolletjestrui-secrets
key: site_password
- name: ADMIN_PASSWORD
valueFrom:
secretKeyRef:
name: bolletjestrui-secrets
key: admin_password
- name: KEY_SECRET
valueFrom:
secretKeyRef:
name: bolletjestrui-secrets
key: key_secret
# Push notifications. optional:true is load-bearing: without it a missing
# key leaves the pod in CreateContainerConfigError and the site is down,
# which would make deploying this depend on the Vault entries landing
# first. The app already treats absent VAPID keys as "send nothing".
- name: VAPID_PUBLIC_KEY
valueFrom:
secretKeyRef:
name: bolletjestrui-secrets
key: vapid_public_key
optional: true
- name: VAPID_PRIVATE_KEY
valueFrom:
secretKeyRef:
name: bolletjestrui-secrets
key: vapid_private_key
optional: true
- name: VAPID_SUBJECT
value: mailto:ruben.hensen@protonmail.com
# Node trusts its built-in roots, which still include the ones
# above the compromised eMudhra intermediates. Use
# patched-ca-bundle through OpenSSL instead until Node ships a fix.
- name: NODE_OPTIONS
value: --use-openssl-ca
- name: SSL_CERT_FILE
value: /etc/ssl/certs/ca-certificates.crt
resources:
requests:
memory: "128Mi"
cpu: "50m"
limits:
memory: "512Mi"
cpu: "500m"
readinessProbe:
httpGet:
path: /login
port: 3000
initialDelaySeconds: 5
periodSeconds: 10
livenessProbe:
httpGet:
path: /login
port: 3000
initialDelaySeconds: 15
periodSeconds: 20
volumeMounts:
- mountPath: /app/data
name: data
- mountPath: /etc/ssl/certs
name: patched-ca-bundle
readOnly: true
restartPolicy: Always
volumes:
- name: data
persistentVolumeClaim:
claimName: bolletjestrui-data
- name: patched-ca-bundle
configMap:
name: patched-ca-bundle
+13
View File
@@ -0,0 +1,13 @@
apiVersion: v1
kind: Service
metadata:
labels:
app: bolletjestrui
name: bolletjestrui
spec:
ports:
- name: "3000"
port: 3000
targetPort: 3000
selector:
app: bolletjestrui
+16
View File
@@ -0,0 +1,16 @@
# The TLS certificate the Gateway serves for this app (see httproute.yaml).
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: letsencrypt-prod
spec:
secretName: letsencrypt-prod
dnsNames:
- vic.rubenhensen.nl
issuerRef:
group: cert-manager.io
kind: ClusterIssuer
name: prod-cluster-issuer
usages:
- digital signature
- key encipherment
@@ -2,11 +2,11 @@ apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
io.kompose.service: app
name: app
app: bolletjestrui
name: bolletjestrui-data
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
storage: 2Gi
+36
View File
@@ -0,0 +1,36 @@
apiVersion: external-secrets.io/v1
kind: ExternalSecret
metadata:
name: bolletjestrui-secrets
spec:
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
refreshInterval: 15m
target:
name: bolletjestrui-secrets
creationPolicy: Owner
data:
- secretKey: site_password
remoteRef:
key: kv/bolletjestrui
property: site_password
- secretKey: admin_password
remoteRef:
key: kv/bolletjestrui
property: admin_password
- secretKey: key_secret
remoteRef:
key: kv/bolletjestrui
property: key_secret
# web-push keypair for the "de route is gekozen" notification.
# Generate once with `npx web-push generate-vapid-keys` and never rotate it:
# a new key invalidates every subscription on everyone's phone.
- secretKey: vapid_public_key
remoteRef:
key: kv/bolletjestrui
property: vapid_public_key
- secretKey: vapid_private_key
remoteRef:
key: kv/bolletjestrui
property: vapid_private_key
+34
View File
@@ -0,0 +1,34 @@
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: bolletjestrui
spec:
parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: https-vic
hostnames:
- vic.rubenhensen.nl
rules:
- backendRefs:
- name: bolletjestrui
port: 3000
# No limit on the whole request, as with nginx. Envoy's default of 15s
# cuts off uploads and long-lived connections.
timeouts:
request: 0s
---
# Lets the Gateway serve the certificate cert-manager keeps in this namespace.
apiVersion: gateway.networking.k8s.io/v1
kind: ReferenceGrant
metadata:
name: gateway-tls
spec:
from:
- group: gateway.networking.k8s.io
kind: Gateway
namespace: envoy-gateway-system
to:
- group: ""
kind: Secret
name: letsencrypt-prod
+56
View File
@@ -0,0 +1,56 @@
# Bolletjestrui faces the internet through Envoy, so its pods only reach each
# other, DNS and the internet: not the LAN (NAS, router), the Kubernetes
# API or other namespaces.
# Ingress comes from Envoy and the node itself (kubelet probes; 10.1.7.64
# is the node's Calico VXLAN address, projectcalico.org/IPv4VXLANTunnelAddr).
# Same layout as mbgwp/networkpolicy.yaml.
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: default
spec:
podSelector: {}
policyTypes:
- Ingress
- Egress
ingress:
- from:
- podSelector: {}
- from:
- ipBlock:
cidr: 192.168.1.204/32
- ipBlock:
cidr: 10.1.7.64/32
- from:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: envoy-gateway-system
podSelector:
matchLabels:
app.kubernetes.io/name: envoy
ports:
- port: 3000
egress:
- to:
- podSelector: {}
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
podSelector:
matchLabels:
k8s-app: kube-dns
ports:
- protocol: UDP
port: 53
- protocol: TCP
port: 53
- to:
- ipBlock:
cidr: 0.0.0.0/0
except:
- 10.0.0.0/8
- 100.64.0.0/10
- 169.254.0.0/16
- 172.16.0.0/12
- 192.168.0.0/16
+5
View File
@@ -0,0 +1,5 @@
apiVersion: v2
name: ca-bundle
description: Puts the patched-ca-bundle ConfigMap in every namespace listed in values.yaml
type: application
version: 0.1.0
File diff suppressed because it is too large. Load diff
+20
View File
@@ -0,0 +1,20 @@
{{- /*
Temporary CA bundle: ca-certificates.crt is /etc/ssl/certs/ca-certificates.crt
from Alpine ca-certificates-bundle 20261020-r0, which drops the roots above
the compromised eMudhra intermediates (https://emudhra.we-have-a-problem.com).
Workloads mount it over /etc/ssl/certs until their images ship a fixed
bundle. Server-side apply keeps the bundle out of the last-applied annotation.
*/}}
{{- range .Values.namespaces }}
---
apiVersion: v1
kind: ConfigMap
metadata:
name: patched-ca-bundle
namespace: {{ . }}
annotations:
argocd.argoproj.io/sync-options: ServerSideApply=true
data:
ca-certificates.crt: |
{{ $.Files.Get "ca-certificates.crt" | indent 4 }}
{{- end }}
+12
View File
@@ -0,0 +1,12 @@
# Namespaces that get the patched-ca-bundle ConfigMap.
namespaces:
- actual-budget
- argocd
- authentik
- bolletjestrui
- cert-manager
- gatus
- gitea
- immich
- ntfy
- serpbear
+5 -2
View File
@@ -14,5 +14,8 @@ spec:
# Enable the HTTP-01 challenge provider
solvers:
- http01:
ingress:
ingressClassName: nginx
gatewayHTTPRoute:
parentRefs:
- name: homelab
namespace: envoy-gateway-system
sectionName: http
-35
View File
@@ -1,35 +0,0 @@
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: daily-backup
namespace: velero
annotations:
velero.io/csi-volumesnapshot-class_driver.longhorn.io: "longhorn-backup-vsc"
spec:
schedule: "0 1 * * *" # Daily at 1 AM
template:
# includedNamespaces:
# - immich
# - nextcloud
# - home-assistant
# - ttrss
ttl: 30d # 30 days
defaultVolumesToFsBackup: true
---
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: weekly-backup
namespace: velero
annotations:
velero.io/csi-volumesnapshot-class_driver.longhorn.io: "longhorn-backup-vsc"
spec:
schedule: "0 0 * * 0" # Weekly on Sunday at midnight
template:
# includedNamespaces:
# - immich
# - nextcloud
# - home-assistant
# - ttrss
ttl: 90d # 90 days
defaultVolumesToFsBackup: true
-131
View File
@@ -1,131 +0,0 @@
# apiVersion: argoproj.io/v1alpha1
# kind: Application
# metadata:
# name: blog-helm
# namespace: argocd
# finalizers:
# - resources-finalizer.argocd.argoproj.io
# spec:
# destination:
# namespace: blog
# server: https://kubernetes.default.svc
# project: default
# source:
# repoURL: registry-1.docker.io/bitnamicharts
# targetRevision: 19.9.0
# chart: ghost
# helm:
# values: |
# image:
# # repository: ghost
# # tag: 5.114.1
# debug: true
# ghostUsername: Ruben
# ## @param existingSecret Name of existing secret containing Ghost credentials
# ## NOTE: Must contain key `ghost-password`
# ## NOTE: When it's set, the `ghostPassword` parameter is ignored
# existingSecret: ghost-es
# ghostEmail: ruben@hensen.io
# ghostBlogTitle: Catch && Compile
# ghostHost: "blog.hensen.io"
# ghostPath: /
# ghostEnableHttps: true
# ## SMTP mail delivery configuration
# ## ref: https://github.com/bitnami/containers/tree/main/bitnami/ghost/#smtp-configuration
# ## @param smtpHost SMTP server host
# ## @param smtpPort SMTP server port
# ## @param smtpUser SMTP username
# ## @param smtpPassword SMTP user password
# ## @param smtpService SMTP service
# ## @param smtpProtocol SMTP protocol (ssl or tls)
# ##
# smtpHost: smtp.hostinger.com
# smtpPort: 587
# smtpUser: ruben@hensen.io
# smtpPassword: "ignored-but-hast-to-exist-else-password-isnt-passed"
# smtpProtocol: tls
# smtpService: hostinger
# ## @param smtpExistingSecret The name of an existing secret with SMTP credentials
# ## NOTE: Must contain key `smtp-password`
# ## NOTE: When it's set, the `smtpPassword` parameter is ignored
# ##
# ## @param extraEnvVars Array with extra environment variables to add to the Ghost container
# ## e.g:
# ## extraEnvVars:
# ## - name: FOO
# ## value: "bar"
# ##
# # extraEnvVars:
# # - name: mail__options__secure
# # value: "false"
# ## @param allowEmptyPassword Allow the container to be started with blank passwords
# allowEmptyPassword: false
# resourcesPreset: "micro"
# containerPorts:
# http: 2368
# https: 2368
# service:
# type: ClusterIP
# ports:
# http: 80
# https: 443
# ingress:
# enabled: true
# ingressClassName: nginx
# hostname: blog.hensen.io
# path: /
# annotations:
# cert-manager.io/cluster-issuer: prod-cluster-issuer
# nginx.ingress.kubernetes.io/proxy-body-size: 1G
# tls: true
# tlsWwwPrefix: false
# selfSigned: false
# persistence:
# enabled: true
# accessModes:
# - ReadWriteOnce
# size: 8Gi
# mysql:
# enabled: true
# architecture: standalone
# ## MySQL Authentication parameters
# ## @param mysql.auth.rootPassword MySQL root password
# ## @param mysql.auth.database MySQL custom database
# ## @param mysql.auth.username MySQL custom user name
# ## @param mysql.auth.password MySQL custom user password
# ## @param mysql.auth.existingSecret Existing secret with MySQL credentials
# ## ref: https://github.com/bitnami/containers/tree/main/bitnami/mysql#setting-the-root-password-on-first-run
# ## https://github.com/bitnami/containers/tree/main/bitnami/mysql/#creating-a-database-on-first-run
# ## https://github.com/bitnami/containers/tree/main/bitnami/mysql/#creating-a-database-user-on-first-run
# auth:
# database: bitnami_ghost
# username: bn_ghost
# existingSecret: ghost-es
# primary:
# ## MySQL Primary Persistence parameters
# ## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
# ## @param mysql.primary.persistence.enabled Enable persistence on MySQL using PVC(s)
# ## @param mysql.primary.persistence.storageClass Persistent Volume storage class
# ## @param mysql.primary.persistence.accessModes [array] Persistent Volume access modes
# ## @param mysql.primary.persistence.size Persistent Volume size
# ##
# persistence:
# enabled: true
# storageClass: ""
# accessModes:
# - ReadWriteOnce
# size: 8Gi
# ## MySQL primary container's resource requests and limits
# ## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
# ## We usually recommend not to specify default resources and to leave this as a conscious
# ## choice for the user. This also increases chances charts run on environments with little
# ## resources, such as Minikube. If you do want to specify resources, uncomment the following
# ## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# ## @param mysql.primary.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, small, medium, large, xlarge, 2xlarge). This is ignored if primary.resources is set (primary.resources is recommended for production)
# resourcesPreset: "small"
# syncPolicy:
# syncOptions:
# - CreateNamespace=true
# automated:
# selfHeal: true
-13
View File
@@ -1,13 +0,0 @@
apiVersion: velero.io/v1
kind: Schedule
metadata:
name: daily-backup3
spec:
schedule: "*/1 * * * *" # Daily at 1 AM
template:
ttl: 1h # 30 days
defaultVolumesToFsBackup: true
snapshotVolumes: true
snapshotMoveData: true
includedNamespaces:
- ttrss
-18
View File
@@ -1,18 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: ente-photos-folder
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: ente-photos
destination:
server: https://kubernetes.default.svc
namespace: ente-photos
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
@@ -1,12 +0,0 @@
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
io.kompose.service: custom-logs
name: custom-logs
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
-83
View File
@@ -1,83 +0,0 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: museum
spec:
replicas: 1
selector:
matchLabels:
app: ente
strategy:
type: Recreate
template:
metadata:
labels:
app: ente
spec:
containers:
- env:
- name: ENTE_DB_HOST
value: "helm-postgresql"
- name: ENTE_DB_PORT
value: "5432"
- name: ENTE_DB_NAME
value: "ente_db"
- name: ENTE_DB_USER
value: "pguser"
- name: ENTE_DB_PASSWORD
valueFrom:
secretKeyRef:
name: ente-photos-config
key: pgpass
- name: ENTE_S3_ARE_LOCAL_BUCKETS
value: "false"
- name: ENTE_S3_ENTE-PHOTOS_KEY
value: "ente-photos-user"
- name: ENTE_S3_ENTE-PHOTOS_SECRET
valueFrom:
secretKeyRef:
name: ente-photos-config
key: miniopass
- name: ENTE_S3_ENTE-PHOTOS_ENDPOINT
value: "minio.hensen.io:3200"
- name: ENTE_S3_ENTE-PHOTOS_REGION
value: "nl"
- name: ENTE_S3_ENTE-PHOTOS_BUCKET
value: "ente-photos"
image: ghcr.io/ente-io/server
name: museum
# command: [ "sh", "-c"]
# # loop forever, outputting "yo" every 5 seconds
# args: ["while true; do echo 'yo' && sleep 5; done;"]
ports:
- containerPort: 8080
protocol: TCP
- containerPort: 2112
protocol: TCP
volumeMounts:
- mountPath: /var/logs
name: custom-logs
- mountPath: /museum.yaml
name: museum-claim1
readOnly: true
- mountPath: /data
name: museum-claim3
readOnly: true
# - args:
# - TCP-LISTEN:3200,fork,reuseaddr
# - TCP:minio:3200
# image: alpine/socat
# name: socat
restartPolicy: Always
volumes:
- name: custom-logs
persistentVolumeClaim:
claimName: custom-logs
- name: museum-claim1
persistentVolumeClaim:
claimName: museum-claim1
readOnly: true
- name: museum-claim3
persistentVolumeClaim:
claimName: museum-claim3
readOnly: true
-36
View File
@@ -1,36 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ente-server-ingress
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "false"
nginx.ingress.kubernetes.io/enable-cors: "true"
nginx.ingress.kubernetes.io/cors-allow-origin: "http://localhost:3000/"
nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, OPTIONS, DELETE"
# If you encounter a redirect loop or are getting a 307 response code
# then you need to force the nginx ingress to connect to the backend using HTTPS.
#
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
namespace: ente-photos
spec:
ingressClassName: nginx
rules:
- host: ente-server.hensen.io
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: ente-service
port:
name: "eightyeighty"
# TLS configuration for HTTPS
tls:
# TLS secretName used on ClusterIssuer
- secretName: letsencrypt-prod
hosts:
- ente-server.hensen.io
-21
View File
@@ -1,21 +0,0 @@
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: template
spec:
refreshInterval: "15s"
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: ente-photos-config
data:
- secretKey: pgpass
remoteRef:
key: ente-photos-postgres
property: password
- secretKey: miniopass
remoteRef:
key: minio-ente-photos-user
property: password
@@ -1,23 +0,0 @@
kind: Deployment
apiVersion: apps/v1
metadata:
name: ente-web
labels:
app: ente-web
# docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
spec:
replicas: 1
selector:
matchLabels:
app: ente-web
template:
metadata:
labels:
app: ente-web
spec:
containers:
- name: ente-web
image: hebury/ente-web:0.2
ports:
- containerPort: 3000
protocol: TCP
-36
View File
@@ -1,36 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: ente-web-ingress
annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "false"
# nginx.ingress.kubernetes.io/enable-cors: "true"
# nginx.ingress.kubernetes.io/cors-allow-origin: "http://localhost:3000/"
# nginx.ingress.kubernetes.io/cors-allow-methods: "PUT, GET, POST, OPTIONS, DELETE"
# If you encounter a redirect loop or are getting a 307 response code
# then you need to force the nginx ingress to connect to the backend using HTTPS.
#
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
namespace: ente-photos
spec:
ingressClassName: nginx
rules:
- host: ente.hensen.io
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: ente-service
port:
name: "https"
# TLS configuration for HTTPS
tls:
# TLS secretName used on ClusterIssuer
- secretName: letsencrypt-prod2
hosts:
- ente.hensen.io
-25
View File
@@ -1,25 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: helm-postgresql
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
syncPolicy:
syncOptions:
- CreateNamespace=true
project: default
sources:
- chart: postgresql
repoURL: registry-1.docker.io/bitnamicharts
targetRevision: 15.5.29
helm:
valueFiles:
- $values/ente-photos/postgres-values.yaml
- repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
ref: values
destination:
server: https://kubernetes.default.svc
namespace: ente-photos
@@ -1,12 +0,0 @@
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
io.kompose.service: museum-claim1
name: museum-claim1
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
@@ -1,12 +0,0 @@
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
labels:
io.kompose.service: museum-claim3
name: museum-claim3
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 100Mi
-14
View File
@@ -1,14 +0,0 @@
apiVersion: v1
kind: Service
metadata:
name: ente-service
spec:
selector:
app: ente
ports:
- name: "eightyeighty"
port: 8080
targetPort: 8080
- name: "2112"
port: 2112
targetPort: 2112
-16
View File
@@ -1,16 +0,0 @@
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: pgadmin-es
namespace: ente-photos
spec:
refreshInterval: "15s"
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: pgadmin-secret
dataFrom:
- extract:
key: pgadmin
-45
View File
@@ -1,45 +0,0 @@
apiVersion: apps/v1
kind: Deployment
metadata:
name: pgadmin
spec:
selector:
matchLabels:
app: pgadmin
replicas: 1
template:
metadata:
labels:
app: pgadmin
spec:
containers:
- name: pgadmin4
image: dpage/pgadmin4
env:
- name: PGADMIN_DEFAULT_EMAIL
value: "admin@admin.com"
- name: PGADMIN_DEFAULT_PASSWORD
valueFrom:
secretKeyRef:
name: pgadmin-secret
key: pgadmin-default-password
- name: PGADMIN_PORT
value: "80"
ports:
- containerPort: 80
name: pgadminport
---
apiVersion: v1
kind: Service
metadata:
name: pgadmin
labels:
app: pgadmin
spec:
selector:
app: pgadmin
type: NodePort
ports:
- port: 80
nodePort: 30200
File diff suppressed because it is too large. Load diff
-16
View File
@@ -1,16 +0,0 @@
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: postgresql-es
namespace: ente-photos
spec:
refreshInterval: "15s"
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: postgres-config
dataFrom:
- extract:
key: ente-photos-postgres
-95
View File
@@ -1,95 +0,0 @@
# apiVersion: argoproj.io/v1alpha1
# kind: Application
# metadata:
# name: mbg-helm
# namespace: argocd
# finalizers:
# - resources-finalizer.argocd.argoproj.io
# spec:
# destination:
# namespace: mbg
# server: https://kubernetes.default.svc
# project: default
# source:
# repoURL: registry-1.docker.io/bitnamicharts
# targetRevision: 24.1.13
# chart: wordpress
# helm:
# values: |
# service:
# ## @param service.type WordPress service type
# ##
# type: ClusterIP
# ingress:
# enabled: true
# ingressClassName: nginx
# hostname: scoutingmbg.nl
# path: /
# annotations:
# cert-manager.io/cluster-issuer: prod-cluster-issuer
# nginx.ingress.kubernetes.io/proxy-body-size: 1G
# tls: true
# tlsWwwPrefix: false
# selfSigned: false
# extraHosts:
# - name: www.scoutingmbg.nl
# extraPaths: []
# extraTls:
# - secretName: letsencrypt-prod
# hosts:
# - scoutingmbg.nl
# - www.scoutingmbg.nl
# secrets: []
# extraRules: []
# persistence:
# ## @param persistence.enabled Enable persistence using Persistent Volume Claims
# ##
# enabled: true
# ## @param persistence.storageClass Persistent Volume storage class
# ## If defined, storageClassName: <storageClass>
# ## If set to "-", storageClassName: "", which disables dynamic provisioning
# ## If undefined (the default) or set to null, no storageClassName spec is set, choosing the default provisioner
# ##
# storageClass: ""
# ## @param persistence.accessModes [array] Persistent Volume access modes
# ##
# accessModes:
# - ReadWriteOnce
# ## @param persistence.accessMode Persistent Volume access mode (DEPRECATED: use `persistence.accessModes` instead)
# ##
# accessMode: ReadWriteOnce
# ## @param persistence.size Persistent Volume size
# ##
# size: 10Gi
# ## @param persistence.dataSource Custom PVC data source
# ##
# dataSource: {}
# ## @param persistence.existingClaim The name of an existing PVC to use for persistence
# ##
# existingClaim: ""
# ## @param persistence.selector Selector to match an existing Persistent Volume for WordPress data PVC
# ## If set, the PVC can't have a PV dynamically provisioned for it
# ## E.g.
# ## selector:
# ## matchLabels:
# ## app: my-app
# ##
# selector: {}
# ## @param persistence.annotations Persistent Volume Claim annotations
# ##
# annotations: {}
# allowEmptyPassword: false
# existingSecret: wordpress-credentials
# wordpressUsername: rubenhensen
# smtpExistingSecret: wordpress-credentials
# customHTAccessCM: prod-wordpress-cm
# resourcesPreset: "large"
# livenessProbe:
# enabled: false
# syncPolicy:
# syncOptions:
# - CreateNamespace=true
# automated:
# selfHeal: true
-20
View File
@@ -1,20 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: minio-folder
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: minio
destination:
server: https://kubernetes.default.svc
namespace: minio
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
-28
View File
@@ -1,28 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: minio-operator
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
prune: true
project: default
sources:
- chart: operator
repoURL: https://operator.min.io
targetRevision: 6.0.3
helm:
valueFiles:
- $values/minio/values-operator.yaml
- repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
ref: values
destination:
server: https://kubernetes.default.svc
namespace: minio-operator
-30
View File
@@ -1,30 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: minio-tenant
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
prune: true
project: default
sources:
- chart: tenant
repoURL: https://operator.min.io
targetRevision: 6.0.3
helm:
valueFiles:
- $values/minio/values-tenant.yaml
- repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
ref: values
destination:
server: https://kubernetes.default.svc
namespace: minio-tenant
-31
View File
@@ -1,31 +0,0 @@
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: minio-tenant-es
namespace: minio-tenant
spec:
refreshInterval: "15s"
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: minio-env-configuration
data:
- secretKey: config.env
remoteRef:
key: minio-tenant-root
property: config.env
# # metadataPolicy to fetch all the labels in JSON format
# - secretKey: tags
# remoteRef:
# metadataPolicy: Fetch
# key: foo
# # metadataPolicy to fetch a specific label (dev) from the source secret
# - secretKey: developer
# remoteRef:
# metadataPolicy: Fetch
# key: foo
# property: dev
-319
View File
@@ -1,319 +0,0 @@
###
# Root key for Operator Helm Chart
operator:
###
# An array of environment variables to pass to the Operator deployment.
# Pass an empty array to start Operator with defaults.
#
# For example:
#
# .. code-block:: yaml
#
# env:
# - name: MINIO_OPERATOR_DEPLOYMENT_NAME
# valueFrom:
# fieldRef:
# fieldPath: metadata.labels['app.kubernetes.io/name']
# - name: MINIO_CONSOLE_TLS_ENABLE
# value: "off"
# - name: CLUSTER_DOMAIN
# value: "cluster.domain"
# - name: WATCHED_NAMESPACE
# value: ""
# - name: MINIO_OPERATOR_RUNTIME
# value: "OpenShift"
#
# See `Operator environment variables <https://github.com/minio/operator/blob/master/docs/env-variables.md>`__ for a list of all supported values.
env:
- name: OPERATOR_STS_ENABLED
value: "on"
###
# Specify the Operator container image to use for the deployment.
# ``image.tag``
# For example, the following sets the image to the ``quay.io/minio/operator`` repo and the v5.0.11 tag.
# The container pulls the image if not already present:
#
# .. code-block:: yaml
#
# image:
# repository: quay.io/minio/operator
# tag: v5.0.11
# pullPolicy: IfNotPresent
#
# The chart also supports specifying an image based on digest value:
#
# .. code-block:: yaml
#
# image:
# repository: quay.io/minio/operator@sha256
# digest: 28c80b379c75242c6fe793dfbf212f43c602140a0de5ebe3d9c2a3a7b9f9f983
# pullPolicy: IfNotPresent
#
image:
repository: quay.io/minio/operator
tag: v5.0.11
pullPolicy: IfNotPresent
###
#
# An array of Kubernetes secrets to use for pulling images from a private ``image.repository``.
# Only one array element is supported at this time.
imagePullSecrets: [ ]
###
#
# The name of a custom `Container Runtime <https://kubernetes.io/docs/concepts/containers/runtime-class/>`__ to use for the Operator pods.
runtimeClassName: ~
###
# An array of `initContainers <https://kubernetes.io/docs/concepts/workloads/pods/init-containers/>`__ to start up before the Operator pods.
# Exercise care as ``initContainer`` failures prevent Operator pods from starting.
# Pass an empty array to start the Operator normally.
initContainers: [ ]
###
# The number of Operator pods to deploy.
# Higher values increase availability in the event of worker node failures.
#
# The cluster must have sufficient number of available worker nodes to fulfill the request.
# Operator pods deploy with pod anti-affinity by default, preventing Kubernetes from scheduling multiple pods onto a single Worker node.
replicaCount: 1
###
# The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Operator resources.
#
# You may need to modify these values to meet your cluster's security and access settings.
securityContext:
runAsUser: 1000
runAsGroup: 1000
runAsNonRoot: true
fsGroup: 1000
###
# The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Operator containers.
# You may need to modify these values to meet your cluster's security and access settings.
containerSecurityContext:
runAsUser: 1000
runAsGroup: 1000
runAsNonRoot: true
###
# An array of `Volumes <https://kubernetes.io/docs/concepts/storage/volumes/>`__ which the Operator can mount to pods.
#
# The volumes must exist *and* be accessible to the Operator pods.
volumes: [ ]
###
# An array of volume mount points associated to each Operator container.
#
# Specify each item in the array as follows:
#
# .. code-block:: yaml
#
# volumeMounts:
# - name: volumename
# mountPath: /path/to/mount
#
# The ``name`` field must correspond to an entry in the ``volumes`` array.
volumeMounts: [ ]
###
# Any `Node Selectors <https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/>`__ to apply to Operator pods.
#
# The Kubernetes scheduler uses these selectors to determine which worker nodes onto which it can deploy Operator pods.
#
# If no worker nodes match the specified selectors, the Operator deployment will fail.
nodeSelector: { }
###
#
# The `Pod Priority <https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/>`__ to assign to Operator pods.
priorityClassName: ""
###
#
# The `affinity <https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/>`__ or anti-affinity settings to apply to Operator pods.
#
# These settings determine the distribution of pods across worker nodes and can help prevent or allow colocating pods onto the same worker nodes.
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: name
operator: In
values:
- minio-operator
topologyKey: kubernetes.io/hostname
###
#
# An array of `Toleration labels <https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/>`__ to associate to Operator pods.
#
# These settings determine the distribution of pods across worker nodes.
tolerations: [ ]
###
#
# An array of `Topology Spread Constraints <https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/>`__ to associate to Operator pods.
#
# These settings determine the distribution of pods across worker nodes.
topologySpreadConstraints: [ ]
###
#
# The `Requests or Limits <https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/>`__ for resources to associate to Operator pods.
#
# These settings can control the minimum and maximum resources requested for each pod.
# If no worker nodes can meet the specified requests, the Operator may fail to deploy.
resources:
requests:
cpu: 200m
memory: 256Mi
ephemeral-storage: 500Mi
###
# Root key for Operator Console
console:
###
# Specify ``false`` to disable the Operator Console.
#
# If the Operator Console is disabled, all management of Operator Tenants must be done through the Kubernetes API.
enabled: true
###
# Specify the Operator Console container image to use for the deployment.
# ``image.tag``
# For example, the following sets the image to the ``quay.io/minio/operator`` repo and the v5.0.11 tag.
# The container pulls the image if not already present:
#
# .. code-block:: yaml
#
# image:
# repository: quay.io/minio/operator
# tag: v5.0.11
# pullPolicy: IfNotPresent
#
# The chart also supports specifying an image based on digest value:
#
# .. code-block:: yaml
#
# image:
# repository: quay.io/minio/operator@sha256
# digest: 28c80b379c75242c6fe793dfbf212f43c602140a0de5ebe3d9c2a3a7b9f9f983
# pullPolicy: IfNotPresent
#
# The specified values should match that of ``operator.image`` to ensure predictable operations.
image:
repository: quay.io/minio/operator
tag: v5.0.11
pullPolicy: IfNotPresent
###
# An array of environment variables to pass to the Operator Console deployment.
# Pass an empty array to start Operator Console with defaults.
env: [ ]
###
#
# An array of Kubernetes secrets to use for pulling images from a private ``image.repository``.
imagePullSecrets: [ ]
###
#
# The name of a custom `Container Runtime <https://kubernetes.io/docs/concepts/containers/runtime-class/>`__ to use for the Operator Console pods.
runtimeClassName: ~
###
# An array of `initContainers <https://kubernetes.io/docs/concepts/workloads/pods/init-containers/>`__ to start up before the Operator Console pods.
# Exercise care as ``initContainer`` failures prevent Console pods from starting.
# Pass an empty array to start the Console normally.
initContainers: [ ]
###
# The number of Operator Console pods to deploy.
# Higher values increase availability in the event of worker node failures.
#
# The cluster must have sufficient number of available worker nodes to fulfill the request.
# Console pods deploy with pod anti-affinity by default, preventing Kubernetes from scheduling multiple pods onto a single Worker node.
replicaCount: 1
###
# Any `Node Selectors <https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/>`__ to apply to Operator Console pods.
#
# The Kubernetes scheduler uses these selectors to determine which worker nodes onto which it can deploy Console pods.
#
# If no worker nodes match the specified selectors, the Console deployment will fail.
nodeSelector: { }
###
#
# The `affinity <https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/>`__ or anti-affinity settings to apply to Operator Console pods.
#
# These settings determine the distribution of pods across worker nodes and can help prevent or allow colocating pods onto the same worker nodes.
affinity:
podAntiAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
- labelSelector:
matchExpressions:
- key: name
operator: In
values:
- minio-operator
topologyKey: kubernetes.io/hostname
###
#
# An array of `Toleration labels <https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/>`__ to associate to Operator Console pods.
#
# These settings determine the distribution of pods across worker nodes.
tolerations: [ ]
###
#
# An array of `Topology Spread Constraints <https://kubernetes.io/docs/concepts/scheduling-eviction/topology-spread-constraints/>`__ to associate to Operator Console pods.
#
# These settings determine the distribution of pods across worker nodes.
topologySpreadConstraints: [ ]
###
#
# The `Requests or Limits <https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/>`__ for resources to associate to Operator Console pods.
#
# These settings can control the minimum and maximum resources requested for each pod.
# If no worker nodes can meet the specified requests, the Console may fail to deploy.
resources:
requests:
cpu: 0.25
memory: 512Mi
###
# The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Operator Console resources.
#
# You may need to modify these values to meet your cluster's security and access settings.
securityContext:
runAsUser: 1000
runAsNonRoot: true
###
# The Kubernetes `SecurityContext <https://kubernetes.io/docs/tasks/configure-pod-container/security-context/>`__ to use for deploying Operator Console containers.
# You may need to modify these values to meet your cluster's security and access settings.
containerSecurityContext:
runAsUser: 1000
runAsNonRoot: true
###
# Configures `Ingress <https://kubernetes.io/docs/concepts/services-networking/ingress/>`__ for the Operator Console.
#
# Set the keys to conform to the Ingress controller and configuration of your choice.
# ingress:
# enabled: true
# ingressClassName: nginx
# labels: { }
# annotations:
# cert-manager.io/cluster-issuer: prod-cluster-issuer
# # nginx.ingress.kubernetes.io/ssl-passthrough: "true"
# nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
# tls:
# # TLS secretName used on ClusterIssuer
# - secretName: letsencrypt-prod
# hosts:
# - minio-console.hensen.io
# host: minio-console.hensen.io
# path: /
# pathType: Prefix
###
# An array of `Volumes <https://kubernetes.io/docs/concepts/storage/volumes/>`__ which the Operator Console can mount to pods.
#
# The volumes must exist *and* be accessible to the Console pods.
volumes:
- name: tmp
emptyDir: {}
###
# An array of volume mount points associated to each Operator Console container.
#
# Specify each item in the array as follows:
#
# .. code-block:: yaml
#
# volumeMounts:
# - name: volumename
# mountPath: /path/to/mount
#
# The ``name`` field must correspond to an entry in the ``volumes`` array.
volumeMounts:
- name: tmp
readOnly: false
mountPath: /tmp/certs/CAs
-120
View File
@@ -1,120 +0,0 @@
tenant:
name: myminio
image:
repository: quay.io/minio/minio
tag: RELEASE.2024-08-17T01-24-54Z
pullPolicy: IfNotPresent
imagePullSecret: { }
scheduler: { }
configuration:
name: minio-env-configuration
configSecret:
existingSecret: true
pools:
- servers: 1
name: pool-0
volumesPerServer: 1
size: 10Gi
storageAnnotations: { }
annotations: { }
labels: { }
tolerations: [ ]
nodeSelector: { }
affinity: { }
resources: { }
securityContext:
runAsUser: 1000
runAsGroup: 1000
fsGroup: 1000
fsGroupChangePolicy: "OnRootMismatch"
runAsNonRoot: true
containerSecurityContext:
runAsUser: 1000
runAsGroup: 1000
runAsNonRoot: true
allowPrivilegeEscalation: false
capabilities:
drop:
- ALL
seccompProfile:
type: RuntimeDefault
topologySpreadConstraints: [ ]
mountPath: /export
subPath: /data
metrics:
enabled: false
port: 9000
protocol: http
certificate:
externalCaCertSecret: [ ]
externalCertSecret: [ ]
requestAutoCert: true
certConfig: { }
features:
bucketDNS: false
domains: { }
enableSFTP: false
buckets: [ ]
users: [ ]
podManagementPolicy: Parallel
liveness: { }
readiness: { }
startup: { }
lifecycle: { }
exposeServices: { }
serviceAccountName: ""
prometheusOperator: false
logging: { }
serviceMetadata: { }
env: [ ]
priorityClassName: ""
additionalVolumes: [ ]
additionalVolumeMounts: [ ]
ingress:
api:
enabled: true
ingressClassName: nginx
# labels: { }
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
tls:
- secretName: letsencrypt-prod
hosts:
- minio.hensen.io
host: minio.hensen.io
path: /
pathType: Prefix
console:
enabled: true
ingressClassName: nginx
# labels: { }
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
nginx.ingress.kubernetes.io/ssl-passthrough: "true"
nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"
tls:
- secretName: letsencrypt-prod-2
hosts:
- minio-console.hensen.io
host: minio-console.hensen.io
path: /
pathType: Prefix
-21
View File
@@ -1,21 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: mist-folder
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: mist
destination:
server: https://kubernetes.default.svc
namespace: mist
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
-32
View File
@@ -1,32 +0,0 @@
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: rowing-webcam-ingress
namespace: default
annotations:
kubernetes.io/ingress.class: "nginx"
nginx.ingress.kubernetes.io/ssl-redirect: "true"
nginx.ingress.kubernetes.io/backend-protocol: "HTTP"
nginx.ingress.kubernetes.io/proxy-body-size: "10m"
cert-manager.io/cluster-issuer: prod-cluster-issuer
# Add basic auth to protect the webcam
# nginx.ingress.kubernetes.io/auth-type: basic
# nginx.ingress.kubernetes.io/auth-secret: rowing-webcam-auth
# nginx.ingress.kubernetes.io/auth-realm: "Rowing Club Webcam"
spec:
ingressClassName: nginx
rules:
- host: mist.hensen.io
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: rowing-webcam-service
port:
number: 80
tls:
- hosts:
- mist.hensen.io
secretName: mist-hensen-io-tls # Make sure this TLS secret exists
-13
View File
@@ -1,13 +0,0 @@
apiVersion: v1
kind: Service
metadata:
name: rowing-webcam-service
namespace: default
spec:
ports:
- port: 80
targetPort: 80
protocol: TCP
# This is an ExternalName service that points to your Raspberry Pi
type: ExternalName
externalName: 192.168.1.201
-108
View File
@@ -1,108 +0,0 @@
# apiVersion: argoproj.io/v1alpha1
# kind: Application
# metadata:
# name: nextcloud-helm
# namespace: argocd
# finalizers:
# - resources-finalizer.argocd.argoproj.io
# spec:
# destination:
# namespace: nextcloud
# server: https://kubernetes.default.svc
# project: default
# source:
# repoURL: https://nextcloud.github.io/helm/
# targetRevision: 6.6.3
# chart: nextcloud
# helm:
# values: |
# persistence:
# # Nextcloud Data (/var/www/html)
# enabled: true
# accessMode: ReadWriteOnce
# size: 100Gi
# resources: {}
# # We usually recommend not to specify default resources and to leave this as a conscious
# # choice for the user. This also increases chances charts run on environments with little
# # resources, such as Minikube. If you do want to specify resources, uncomment the following
# # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# # limits:
# # cpu: 100m
# # memory: 128Mi
# # requests:
# # cpu: 100m
# # memory: 128Mi
# nextcloud:
# host: drive.hensen.io
# configs:
# proxy.config.php: |
# <?php
# $CONFIG = array (
# 'trusted_proxies' => ['10.0.0.0/8', '192.168.1.1/32'],
# );
# phone.config.php: |
# <?php
# $CONFIG = array (
# 'default_phone_region' => 'NL',
# );
# phpConfigs:
# user.ini: |-
# upload_max_filesize=16G
# post_max_size=16G
# livenessProbe:
# enabled: false
# readinessProbe:
# enabled: false
# phpClientHttpsFix:
# enabled: true
# protocol: https
# ingress:
# enabled: true
# className: nginx
# annotations:
# nginx.ingress.kubernetes.io/proxy-body-size: 100G
# nginx.ingress.kubernetes.io/configuration-snippet: |
# more_set_headers "Strict-Transport-Security: max-age=15768000; includeSubDomains";
# # kubernetes.io/tls-acme: "true"
# cert-manager.io/cluster-issuer: prod-cluster-issuer
# # # Keep this in sync with the README.md:
# # nginx.ingress.kubernetes.io/server-snippet: |
# # server_tokens off
# # proxy_hide_header X-Powered-By;
# # rewrite ^/.well-known/webfinger /index.php/.well-known/webfinger last;
# # rewrite ^/.well-known/nodeinfo /index.php/.well-known/nodeinfo last;
# # rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
# # rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json;
# # location = /.well-known/carddav {
# # return 301 $scheme://$host/remote.php/dav;
# # }
# # location = /.well-known/caldav {
# # return 301 $scheme://$host/remote.php/dav;
# # }
# # location = /robots.txt {
# # allow all;
# # log_not_found off;
# # access_log off;
# # }
# # location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
# # deny all;
# # }
# # location ~ ^/(?:autotest|occ|issue|indie|db_|console) {
# # deny all;
# # }
# tls:
# - secretName: nextcloud-tls
# hosts:
# - drive.hensen.io
# labels: {}
# path: /
# pathType: Prefix
# syncPolicy:
# syncOptions:
# - CreateNamespace=true
# automated:
# selfHeal: true
-21
View File
@@ -1,21 +0,0 @@
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: owntracks-folder
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
spec:
project: default
source:
repoURL: https://github.com/rubenhensen/k8scd.git
targetRevision: HEAD
path: owntracks
destination:
server: https://kubernetes.default.svc
namespace: owntracks
syncPolicy:
syncOptions:
- CreateNamespace=true
automated:
selfHeal: true
-167
View File
@@ -1,167 +0,0 @@
# apiVersion: argoproj.io/v1alpha1
# kind: Application
# metadata:
# name: mosquitto-helm
# namespace: argocd
# finalizers:
# - resources-finalizer.argocd.argoproj.io
# spec:
# syncPolicy:
# syncOptions:
# - CreateNamespace=true
# automated:
# prune: true
# selfHeal: true
# project: default
# sources:
# - chart: mosquitto
# repoURL: https://storage.googleapis.com/t3n-helm-charts
# targetRevision: v2.4.1 # Replace with the Longhorn version you'd like to install or upgrade to
# helm:
# values: |
# replicaCount: 1
# strategyType: Recreate
# image:
# repository: eclipse-mosquitto
# tag: 1.6.12
# pullPolicy: IfNotPresent
# imagePullSecrets: []
# nameOverride: ""
# fullnameOverride: ""
# serviceAccount:
# # Specifies whether a service account should be created
# create: true
# # The name of the service account to use.
# # If not set and create is true, a name is generated using the fullname template
# name:
# service:
# type: ClusterIP
# externalTrafficPolicy: null
# annotations: {}
# # metallb.universe.tf/allow-shared-ip: pi-hole
# ports:
# mqtt:
# port: 1883
# # sets consistent nodePort, required to set service.type=NodePort
# # nodePort: 31883
# protocol: TCP
# websocket:
# port: 9090
# protocol: TCP
# persistence:
# enabled: true
# accessMode: ReadWriteOnce
# existingClaim: ""
# mountPath: /mosquitto/data
# subPath: ""
# ## database data Persistent Volume Storage Class
# ## If defined, storageClassName: <storageClass>
# ## If set to "-", storageClassName: "", which disables dynamic provisioning
# ## If undefined (the default) or set to null, no storageClassName spec is
# ## set, choosing the default provisioner. (gp2 on AWS, standard on
# ## GKE, AWS & OpenStack)
# ##
# # storageClass: "-"
# size: 1Gi
# resources: {}
# # We usually recommend not to specify default resources and to leave this as a conscious
# # choice for the user. This also increases chances charts run on environments with little
# # resources, such as Minikube. If you do want to specify resources, uncomment the following
# # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
# # limits:
# # cpu: 100m
# # memory: 128Mi
# # requests:
# # cpu: 100m
# # memory: 128Mi
# podSecurityContext: {}
# # runAsUser: 1001
# # fsGroup: 10000
# securityContext: {}
# # runAsUser: 1001
# # fsGroup: 10000
# nodeSelector: {}
# tolerations: []
# affinity: {}
# authentication:
# passwordEntries: ""
# # To use authentication with mosquitto, you can set a list of password entries to be used.
# # reference https://mosquitto.org/man/mosquitto_passwd-1.html to generate these entries.
# # For example:
# # passwordEntries: |-
# # user1:$6$BKzw0RKerxV4Esbj$Uz5slWGB1TiOtYIEokEl0eR1YSEQAdKpcdRYMsLYbwjktlVzdLyGk41YCPGyMLnBePtdwPhkcm8kjGI0R9s57w==
# # user2:$6$b5vYuHrSLj48Ii32$NjlbnatIaUQSsNvxxTpawpav6NPyZ8QhGrdEVGtyU1rgEGjNzVGKlstRg29FV6MFTPs/ugPA8D5I5+qRcIMXSg==
# passwordFilePath: "/etc/mosquitto/passwordfile"
# authorization:
# acls: ""
# # To use authorizations with mosquitto, you can set a list of per user or pattern-based rules.
# # reference https://mosquitto.org/man/mosquitto-conf-5.html for further information.
# # For example:
# # acls: |-
# # zigbee2mqtt ACLs
# # user zigbee2mqtt
# # topic readwrite zigbee2mqtt/#
# # topic readwrite homeassistant/#
# # Tasmota-compatible ACLs
# # pattern read cmnd/%u/#
# # pattern write stat/%u/#
# # pattern write tele/%u/#
# aclfilePath: "/etc/mosquitto/aclfile"
# existingConfigMap: ""
# config: |
# persistence true
# persistence_location /mosquitto/data/
# log_dest stdout
# listener 1883
# listener 9090
# protocol websockets
# ## Additional volumes.
# extraVolumes: []
# # - name: tls
# # secret:
# # secretName: mosquitto-certs
# ## Additional volumeMounts to the main container.
# extraVolumeMounts: []
# # - name: tls
# # mountPath: /certs
# # subPath: cafile
# monitoring:
# podMonitor:
# enabled: false
# sidecar:
# enabled: false
# port: 9234
# # nodePort: 32234
# image:
# repository: nolte/mosquitto-exporter
# tag: v0.6.3
# pullPolicy: IfNotPresent
# resources:
# limits:
# cpu: 300m
# memory: 128Mi
# requests:
# cpu: 100m
# memory: 64Mi
# destination:
# server: https://kubernetes.default.svc
# namespace: owntracks
-279
View File
@@ -1,279 +0,0 @@
---
# PersistentVolumeClaim for OwnTracks Recorder
# apiVersion: v1
# kind: PersistentVolumeClaim
# metadata:
# name: otrecorder-config-pvc
# spec:
# accessModes:
# - ReadWriteOnce
# resources:
# requests:
# storage: 1Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: otrecorder-store-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 5Gi
---
# PersistentVolumeClaim for Mosquitto
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mosquitto-data-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mosquitto-logs-pvc
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 1Gi
---
# ExternalSecret for OwnTracks Recorder password
# apiVersion: external-secrets.io/v1beta1
# kind: ExternalSecret
# metadata:
# name: owntracks-mqtt-credentials
# spec:
# refreshInterval: "15m"
# secretStoreRef:
# name: vault-backend
# kind: ClusterSecretStore
# target:
# name: owntracks-mqtt-password
# creationPolicy: Owner
# data:
# - secretKey: password
# remoteRef:
# key: kv/mqtt
# property: password
---
# Deployment for OwnTracks Recorder
# apiVersion: apps/v1
# kind: Deployment
# metadata:
# name: otrecorder
# spec:
# replicas: 1
# selector:
# matchLabels:
# app: otrecorder
# template:
# metadata:
# labels:
# app: otrecorder
# spec:
# containers:
# - name: otrecorder
# image: owntracks/recorder
# ports:
# - containerPort: 8083
# env:
# - name: OTR_HOST
# value: "mqtt"
# - name: OTR_PORT
# value: "8883"
# - name: OTR_USER
# value: "ruben"
# # - name: TZ
# # value: "Europe/Berlin"
# # - name: VIRTUAL_HOST
# # value: "owntracks.hensen.io"
# # - name: VIRTUAL_PORT
# # value: 8883
# # - name: OTR_CLIENTID
# # value: ""
# - name: OTR_PASS
# valueFrom:
# secretKeyRef:
# name: owntracks-mqtt-password
# key: password
# volumeMounts:
# - name: store
# mountPath: /store
# volumes:
# - name: store
# persistentVolumeClaim:
# claimName: otrecorder-store-pvc
---
# Service for OwnTracks Recorder
# apiVersion: v1
# kind: Service
# metadata:
# name: otrecorder
# spec:
# selector:
# app: otrecorder
# ports:
# - port: 8083
# targetPort: 8083
# type: ClusterIP
---
# ExternalSecret to fetch MQTT password file from Vault
apiVersion: external-secrets.io/v1beta1
kind: ExternalSecret
metadata:
name: mqtt-password-file
spec:
refreshInterval: "15m"
secretStoreRef:
name: vault-backend
kind: ClusterSecretStore
target:
name: mqtt-password-secret
creationPolicy: Owner
data:
- secretKey: password_file
remoteRef:
key: kv/mqtt
property: secret
---
# ConfigMap for MQTT configuration
apiVersion: v1
kind: ConfigMap
metadata:
name: mqtt-config
data:
mosquitto.conf: |
listener 8883
allow_anonymous false
password_file /mosquitto/config/password_file
# Add other MQTT configuration options here
listener 8083
protocol websockets
---
# MQTT Deployment
apiVersion: apps/v1
kind: Deployment
metadata:
name: mqtt
labels:
app: mqtt
spec:
replicas: 1
selector:
matchLabels:
app: mqtt
template:
metadata:
labels:
app: mqtt
spec:
containers:
- name: mqtt
image: eclipse-mosquitto:latest
ports:
- containerPort: 8883
name: mqtt
- containerPort: 8083
name: websocket
volumeMounts:
- name: config
mountPath: /mosquitto/config/mosquitto.conf
subPath: mosquitto.conf
- name: password-file
mountPath: /mosquitto/config/password_file
subPath: password_file
volumes:
- name: config
configMap:
name: mqtt-config
- name: password-file
secret:
secretName: mqtt-password-secret
---
# MQTT Service
apiVersion: v1
kind: Service
metadata:
name: mqtt
spec:
selector:
app: mqtt
ports:
- port: 8883
targetPort: 8883
name: mqtt
- port: 8083
targetPort: 8083
name: websocket
---
# External access with Ingress for OwnTracks Recorder
# apiVersion: networking.k8s.io/v1
# kind: Ingress
# metadata:
# name: otrecorder-ingress
# annotations:
# nginx.ingress.kubernetes.io/rewrite-target: /
# cert-manager.io/cluster-issuer: prod-cluster-issuer
# spec:
# ingressClassName: nginx
# tls:
# - hosts:
# - owntracks.hensen.io
# secretName: owntracks-tls-secret
# rules:
# - host: owntracks.hensen.io
# http:
# paths:
# - path: /
# pathType: Prefix
# backend:
# service:
# name: otrecorder
# port:
# number: 8083
---
# Corrected MQTT Ingress:
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: mqtt-ingress
annotations:
cert-manager.io/cluster-issuer: prod-cluster-issuer
# Add NGINX TCP passthrough annotations
nginx.ingress.kubernetes.io/ssl-passthrough: "false"
nginx.ingress.kubernetes.io/backend-protocol: "TCP"
nginx.ingress.kubernetes.io/ssl-redirect: "false"
spec:
ingressClassName: nginx
tls:
- hosts:
- mqtt.hensen.io
secretName: mqtt-tls-secret
rules:
- host: mqtt.hensen.io
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: mqtt
port:
number: 8083
# Note: For proper MQTT over TLS, consider these alternatives:
# 1. Use a TCP Load Balancer instead of an Ingress
# 2. Configure the MQTT broker to use TLS directly (port 8883)
# 3. Use NGINX TCP ingress controller configuration
-1
View File
@@ -1 +0,0 @@
Example container to restore files. See `Obsidian > Cluster > Restore longhorn backup` for more
@@ -1,30 +0,0 @@
kind: Deployment
apiVersion: apps/v1
metadata:
name: restore-ubuntu
labels:
app: restore-ubuntu
# namespace: immich # edit in apps folder
# docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1
spec:
replicas: 1
selector:
matchLabels:
app: restore-ubuntu
template:
metadata:
labels:
app: restore-ubuntu
spec:
containers:
- name: restore-ubuntu
image: ubuntu:plucky
volumeMounts:
- name: restorevol
mountPath: /mnt/restorevol/
command: [ "/bin/bash", "-c", "--" ] # Let container sleep, so it does not close because of 'completion'
args: [ "while true; do sleep 30; done;" ]
volumes:
- name: restorevol
persistentVolumeClaim:
claimName: backupofimmich
Loaded 100 of 269 files, more files were not shown because too many files have changed in this diff. Show more