mirror of
https://github.com/rubenhensen/k8scd.git
synced 2026-11-16 14:29:09 +01:00
Compare commits
1
Commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
57b24b5b5c |
No files matched your search
@@ -55,29 +55,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -135,29 +135,3 @@ spec:
|
|||||||
cidr: 192.168.1.204/32
|
cidr: 192.168.1.204/32
|
||||||
ports:
|
ports:
|
||||||
- port: 16443
|
- port: 16443
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -54,29 +54,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
+30
-57
@@ -10,11 +10,11 @@ One node: opti1, an OptiPlex 5060 with an i5-8600T, 32 GB and one 1 TB
|
|||||||
SATA SSD that is 72% full. microk8s v1.36.5 from 1.36/edge, snap held.
|
SATA SSD that is 72% full. microk8s v1.36.5 from 1.36/edge, snap held.
|
||||||
35 Argo CD apps (with metrics-server), all Synced/Healthy; every Longhorn
|
35 Argo CD apps (with metrics-server), all Synced/Healthy; every Longhorn
|
||||||
volume has one replica. authentik 2026.8.5, Vault 2.2.1. Backups go to the
|
volume has one replica. authentik 2026.8.5, Vault 2.2.1. Backups go to the
|
||||||
NAS (192.168.1.99): Longhorn to NFS at 00:00 (7 kept), Velero to Garage
|
NAS (192.168.1.99): Longhorn to NFS at 00:00 (7 kept), Velero to MinIO at
|
||||||
(MinIO until 2026-10-26) at 01:00 (daily kept 30 days, weekly 90 days).
|
01:00 (daily kept 30 days, weekly 90 days). Gatus on s1 (node001, Hetzner)
|
||||||
Gatus on s1 (node001, Hetzner) and s2 (home) watch each other and alert
|
and s2 (home) watch each other and alert through ntfy; s2 also gets an
|
||||||
through ntfy; s2 also gets an hourly report from inside the cluster on the
|
hourly report from inside the cluster on the backups, Vault's seal, the
|
||||||
backups, Vault's seal, the Argo CD apps and the CNPG clusters.
|
Argo CD apps and the CNPG clusters.
|
||||||
Every app namespace has NetworkPolicies, and CI renders and validates all
|
Every app namespace has NetworkPolicies, and CI renders and validates all
|
||||||
apps on every PR. node001 runs mail and tunnels the public hosts home.
|
apps on every PR. node001 runs mail and tunnels the public hosts home.
|
||||||
|
|
||||||
@@ -63,25 +63,24 @@ belong to the group.
|
|||||||
There is no off-site copy (2026-10-25). The plan: swap S3 buckets with a
|
There is no off-site copy (2026-10-25). The plan: swap S3 buckets with a
|
||||||
friend.
|
friend.
|
||||||
|
|
||||||
- [ ] Ours to his bucket: `rclone sync` from Garage's `velero-backups`
|
- [ ] Ours to his bucket: Hyper Backup on the Synology, destination "S3
|
||||||
(~190 GB) to his bucket through an rclone `crypt` remote, in Docker on
|
Storage" with his endpoint as a custom server. Client-side encryption
|
||||||
the NAS like the copy from MinIO (see 5). Encrypted on our side: the
|
on: the kopia repositories use Velero's default password
|
||||||
kopia repositories use Velero's default password (`static-passw0rd`),
|
(`static-passw0rd`), so without it he could read everything, the
|
||||||
so without it he could read everything, the group's photos included.
|
group's photos included. Keep the encryption key next to the Vault
|
||||||
Keep the crypt passwords next to the Vault unseal key. Daily after the
|
unseal key. Source: the shared folder with MinIO's `velero-backups`
|
||||||
Velero backup, ntfy on failure. Hyper Backup, the earlier plan, backs up
|
bucket (~150-200 GB). Daily after the Velero backup, Smart Recycle,
|
||||||
shared folders; Garage keeps its objects as blocks plus a metadata
|
mail on failure
|
||||||
database, and a copy of that folder taken while Garage runs is not
|
|
||||||
consistent
|
|
||||||
- [ ] Needed from him: endpoint, which S3 server he runs, space (~200 GB
|
- [ ] Needed from him: endpoint, which S3 server he runs, space (~200 GB
|
||||||
now, 500 GB to grow), and versioning or object lock on the bucket, so
|
now, 500 GB to grow), and versioning or object lock on the bucket, so
|
||||||
whoever takes over the NAS can't delete the off-site copy as well
|
whoever takes over the NAS can't delete the off-site copy as well
|
||||||
- [ ] His backups with us: a bucket and key for him, with a quota, in the
|
- [ ] His backups with us: Garage (not MinIO, see 5) in Container Manager
|
||||||
Garage on the NAS (`nas/garage`, see 5). Only the S3 API public, as
|
on the Synology, in its own shared folder, with a bucket and key for him
|
||||||
`s3.rubenhensen.nl` through node001 and Envoy with a cert-manager
|
and a quota. Only the S3 API public, as `s3.rubenhensen.nl` through
|
||||||
certificate; the admin API stays on the LAN. The cluster side (DNS,
|
node001 and Envoy with a cert-manager certificate; the admin API stays
|
||||||
node001 tunnel, Certificate, HTTPRoute) goes in git. Needed: how much
|
on the LAN. The cluster side (DNS, node001 tunnel, Certificate,
|
||||||
space he wants, free space on the NAS
|
HTTPRoute) goes in git. Needed: how much space he wants, free space on
|
||||||
|
the NAS
|
||||||
- [ ] Decide which copy of the immich library goes off-site (see 5)
|
- [ ] Decide which copy of the immich library goes off-site (see 5)
|
||||||
- [ ] A restore test that runs on a schedule. `backup-testing/` predates
|
- [ ] A restore test that runs on a schedule. `backup-testing/` predates
|
||||||
Envoy Gateway and still rewrites `*.hensen.io` and bypasses sol-auth.
|
Envoy Gateway and still rewrites `*.hensen.io` and bypasses sol-auth.
|
||||||
@@ -109,12 +108,9 @@ friend.
|
|||||||
MinIO runs region `minio`; the script now reads endpoint, region and
|
MinIO runs region `minio`; the script now reads endpoint, region and
|
||||||
bucket from Velero's location. Copying freshrss's kopia repository took
|
bucket from Velero's location. Copying freshrss's kopia repository took
|
||||||
14 of the ~17 minutes
|
14 of the ~17 minutes
|
||||||
- [x] Ran it again on 2026-10-26 against the copy in Garage
|
- [ ] Run it on a schedule. It needs Docker and the MinIO key, so not in
|
||||||
(daily-backup-20261026010028, same namespaces), before Velero switched
|
the cluster itself: the Mac (launchd) or node001, ideally with a
|
||||||
over (see 5): passed, in 5 minutes instead of 17
|
read-only MinIO user
|
||||||
- [ ] Run it on a schedule. It needs Docker and an S3 key, so not in the
|
|
||||||
cluster itself: the Mac (launchd) or node001, ideally with a read-only
|
|
||||||
Garage key (`garage key create`, `garage bucket allow --read`)
|
|
||||||
|
|
||||||
### 3. authentik 2026.2.1 → 2026.8.5
|
### 3. authentik 2026.2.1 → 2026.8.5
|
||||||
|
|
||||||
@@ -197,7 +193,7 @@ Findings from 2026-10-25:
|
|||||||
- Velero copies the CNPG and MariaDB data directories file by file while
|
- Velero copies the CNPG and MariaDB data directories file by file while
|
||||||
the databases run, which is not a consistent copy. The Longhorn backups
|
the databases run, which is not a consistent copy. The Longhorn backups
|
||||||
start from a snapshot and are crash-consistent. CNPG can back up to
|
start from a snapshot and are crash-consistent. CNPG can back up to
|
||||||
Garage itself (barman cloud plugin), with point-in-time recovery.
|
MinIO itself (barman cloud plugin), with point-in-time recovery.
|
||||||
- The PartiallyFailed daily backup of 10-23 (emptyDirs of Velero's own
|
- The PartiallyFailed daily backup of 10-23 (emptyDirs of Velero's own
|
||||||
maintenance job pods) was fixed that afternoon by
|
maintenance job pods) was fixed that afternoon by
|
||||||
`velero/skip-emptydir-policy.yaml`.
|
`velero/skip-emptydir-policy.yaml`.
|
||||||
@@ -205,31 +201,10 @@ Findings from 2026-10-25:
|
|||||||
- [ ] Whether the immich library stays in Velero. It stays for now
|
- [ ] Whether the immich library stays in Velero. It stays for now
|
||||||
(2026-10-25); decide again with the off-site copy (2)
|
(2026-10-25); decide again with the off-site copy (2)
|
||||||
- [ ] CNPG backups through the barman cloud plugin
|
- [ ] CNPG backups through the barman cloud plugin
|
||||||
- [x] Velero's target, MinIO on the NAS, is no longer maintained: no
|
- [ ] Velero's target, MinIO on the NAS, is no longer maintained: no
|
||||||
community images since October 2025, maintenance mode since December
|
community images since October 2025, maintenance mode since December
|
||||||
2025, and the repository is archived. Since 2026-10-26 Velero backs up
|
2025, and the repository is archived. Move Velero to the Garage from 2
|
||||||
to Garage on the same NAS (`nas/garage`, PR #35). The bucket was copied
|
and switch MinIO off
|
||||||
with rclone (185 GiB in about 6 hours, then a catch-up sync just before
|
|
||||||
the switch), so the existing backups and kopia repositories carried on:
|
|
||||||
after the switch all 55 backups were still listed, and a manual backup
|
|
||||||
of ntfy found the existing repository and used the night's snapshot as
|
|
||||||
its parent. Two things made the NAS slow during the copy: Garage on
|
|
||||||
LMDB with `metadata_fsync`, ~270 disk writes/s while idle (now SQLite,
|
|
||||||
see `nas/garage/garage.toml`), and MinIO's scanner, which kept one disk
|
|
||||||
at 97% busy. The scanner is now at `slowest` (`mc admin config set local
|
|
||||||
scanner speed=slowest` in the MinIO container); it may have slowed
|
|
||||||
Velero's backups to MinIO as well
|
|
||||||
- [ ] Switch MinIO off once Velero has run on Garage for a week (from
|
|
||||||
2026-11-02): stop the container, then delete `/volume1/minio` (343 GiB)
|
|
||||||
and the hand-made Secret `velero/cloud-credentials` (MinIO's key). Only
|
|
||||||
MinIO still has the kopia repositories of namespaces that are gone
|
|
||||||
(~156 GB: nextcloud, ttrss, whisper-priv, whisper-webui, blog, ghost,
|
|
||||||
mbg-wordpress, sogo, sogo-mail, outrun-game, owntracks); decide first
|
|
||||||
whether any of them is worth keeping
|
|
||||||
- [ ] Garage's SQLite WAL (`meta/db.sqlite-wal`) was 1.7 GB on
|
|
||||||
2026-10-26 next to a 270 MB database, and going by the folders in
|
|
||||||
`meta/snapshots`, each 6-hourly metadata snapshot takes about 70
|
|
||||||
minutes. Not growing; check again after a week of normal use
|
|
||||||
|
|
||||||
### 6. Monitoring
|
### 6. Monitoring
|
||||||
|
|
||||||
@@ -348,10 +323,8 @@ Counted 2026-10-25 over the 73 running containers:
|
|||||||
|
|
||||||
### 8. Renovate and CI
|
### 8. Renovate and CI
|
||||||
|
|
||||||
On 2026-10-25 10 Renovate PRs were open, the oldest from February, and
|
10 Renovate PRs are open, the oldest from February, and nothing checks a
|
||||||
nothing checked a PR before Argo CD applied it. All of them have since been
|
PR before Argo CD applies it.
|
||||||
merged or closed (below), none are open (checked 2026-10-25), and CI checks
|
|
||||||
every PR.
|
|
||||||
|
|
||||||
- [x] `.github/workflows/validate.yaml` runs `tools/ci/validate.py` on
|
- [x] `.github/workflows/validate.yaml` runs `tools/ci/validate.py` on
|
||||||
every PR and push (2026-10-25): it renders all 36 apps the way Argo CD
|
every PR and push (2026-10-25): it renders all 36 apps the way Argo CD
|
||||||
@@ -473,7 +446,7 @@ critical / high:
|
|||||||
| tensorchord/cloudnative-vectorchord:17.11-1.1.1 | 17 | 136 | immich's database; look for a newer tag |
|
| tensorchord/cloudnative-vectorchord:17.11-1.1.1 | 17 | 136 | immich's database; look for a newer tag |
|
||||||
| longhornio/longhorn-instance-manager:v1.7.3 | 11 | 159 | still serves 16 volumes, see below |
|
| longhornio/longhorn-instance-manager:v1.7.3 | 11 | 159 | still serves 16 volumes, see below |
|
||||||
| actualbudget/actual-server:26.6.0 | 8 | 83 | chart 1.8.9; Renovate now covers it |
|
| actualbudget/actual-server:26.6.0 | 8 | 83 | chart 1.8.9; Renovate now covers it |
|
||||||
| gitea/gitea:1.27.3 | 8 | 43 | now 28.2.0 (PR #26, 2026-10-25); not scanned again |
|
| gitea/gitea:1.27.3 | 8 | 43 | PR #26 (28.2.0) |
|
||||||
| immich-server / machine-learning v3.3.5 | 7, 7 | 113, 78 | a newer immich release |
|
| immich-server / machine-learning v3.3.5 | 7, 7 | 113, 78 | a newer immich release |
|
||||||
| towfiqi/serpbear:3.1.0 | 6 | 77 | a newer release |
|
| towfiqi/serpbear:3.1.0 | 6 | 77 | a newer release |
|
||||||
| rubenhensen/bolletjestrui:main-10268f1 | 5 | 76 | rebuild on a current base image |
|
| rubenhensen/bolletjestrui:main-10268f1 | 5 | 76 | rebuild on a current base image |
|
||||||
|
|||||||
@@ -56,29 +56,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -1,23 +0,0 @@
|
|||||||
# node001 passes TLS for the tunneled hosts through without opening it, so
|
|
||||||
# without this every request arrives from 46.224.26.65. Wordfence locks that
|
|
||||||
# address out after 20 failed logins (2026-10-26), and with it everyone who
|
|
||||||
# logs in to scoutingmbg.nl. node001 puts a PROXY header with the visitor's
|
|
||||||
# address in front of each connection; Envoy takes the address from there
|
|
||||||
# and adds it to X-Forwarded-For.
|
|
||||||
#
|
|
||||||
# Optional, because s2 and ntfy2 point straight at home and their clients
|
|
||||||
# send no header, and neither does node001's proxy on port 80. The price:
|
|
||||||
# whoever connects to the home address directly can send a header of their
|
|
||||||
# own and claim any address.
|
|
||||||
apiVersion: gateway.envoyproxy.io/v1alpha1
|
|
||||||
kind: ClientTrafficPolicy
|
|
||||||
metadata:
|
|
||||||
name: proxy-protocol
|
|
||||||
namespace: envoy-gateway-system
|
|
||||||
spec:
|
|
||||||
targetRefs:
|
|
||||||
- group: gateway.networking.k8s.io
|
|
||||||
kind: Gateway
|
|
||||||
name: homelab
|
|
||||||
proxyProtocol:
|
|
||||||
optional: true
|
|
||||||
@@ -83,29 +83,3 @@ spec:
|
|||||||
cidr: 192.168.1.204/32
|
cidr: 192.168.1.204/32
|
||||||
ports:
|
ports:
|
||||||
- port: 16443
|
- port: 16443
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -55,29 +55,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -100,29 +100,3 @@ spec:
|
|||||||
cidr: 192.168.1.204/32
|
cidr: 192.168.1.204/32
|
||||||
ports:
|
ports:
|
||||||
- port: 16443
|
- port: 16443
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -8,7 +8,7 @@ spec:
|
|||||||
name: mbgwp-mariadb-credentials
|
name: mbgwp-mariadb-credentials
|
||||||
key: root-password
|
key: root-password
|
||||||
|
|
||||||
image: mariadb:11.4.5
|
image: mariadb:11.8.9
|
||||||
imagePullPolicy: IfNotPresent
|
imagePullPolicy: IfNotPresent
|
||||||
|
|
||||||
port: 3306
|
port: 3306
|
||||||
|
|||||||
@@ -85,29 +85,3 @@ spec:
|
|||||||
kubernetes.io/metadata.name: mariadb-system
|
kubernetes.io/metadata.name: mariadb-system
|
||||||
ports:
|
ports:
|
||||||
- port: 3306
|
- port: 3306
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -173,18 +173,12 @@ in
|
|||||||
# - mail.rubenhensen.nl (and anything else) → local stalwart on 8443
|
# - mail.rubenhensen.nl (and anything else) → local stalwart on 8443
|
||||||
# - tunneled hosts → home cluster ingress on 443
|
# - tunneled hosts → home cluster ingress on 443
|
||||||
# - s1 / ntfy1.rubenhensen.nl → local nginx on 8444 (Gatus, ntfy)
|
# - s1 / ntfy1.rubenhensen.nl → local nginx on 8444 (Gatus, ntfy)
|
||||||
#
|
|
||||||
# Each connection starts with a PROXY header that carries the visitor's
|
|
||||||
# address, so the home cluster sees who is asking instead of this box
|
|
||||||
# (gateway/proxy-protocol.yaml in k8scd). nginx sends the header to
|
|
||||||
# every upstream or none, so the local ones go through a hop on
|
|
||||||
# 8445/8446 that takes it off again.
|
|
||||||
streamConfig = ''
|
streamConfig = ''
|
||||||
map $ssl_preread_server_name $tunnel_upstream {
|
map $ssl_preread_server_name $tunnel_upstream {
|
||||||
${sniMapEntries}
|
${sniMapEntries}
|
||||||
s1.rubenhensen.nl 127.0.0.1:8446;
|
s1.rubenhensen.nl 127.0.0.1:8444;
|
||||||
ntfy1.rubenhensen.nl 127.0.0.1:8446;
|
ntfy1.rubenhensen.nl 127.0.0.1:8444;
|
||||||
default 127.0.0.1:8445;
|
default 127.0.0.1:8443;
|
||||||
}
|
}
|
||||||
|
|
||||||
server {
|
server {
|
||||||
@@ -192,17 +186,6 @@ ${sniMapEntries}
|
|||||||
listen [::]:443;
|
listen [::]:443;
|
||||||
proxy_pass $tunnel_upstream;
|
proxy_pass $tunnel_upstream;
|
||||||
ssl_preread on;
|
ssl_preread on;
|
||||||
proxy_protocol on;
|
|
||||||
}
|
|
||||||
|
|
||||||
server {
|
|
||||||
listen 127.0.0.1:8445 proxy_protocol;
|
|
||||||
proxy_pass 127.0.0.1:8443;
|
|
||||||
}
|
|
||||||
|
|
||||||
server {
|
|
||||||
listen 127.0.0.1:8446 proxy_protocol;
|
|
||||||
proxy_pass 127.0.0.1:8444;
|
|
||||||
}
|
}
|
||||||
'';
|
'';
|
||||||
|
|
||||||
|
|||||||
@@ -65,29 +65,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -54,29 +54,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -66,29 +66,3 @@ spec:
|
|||||||
- 169.254.0.0/16
|
- 169.254.0.0/16
|
||||||
- 172.16.0.0/12
|
- 172.16.0.0/12
|
||||||
- 192.168.0.0/16
|
- 192.168.0.0/16
|
||||||
---
|
|
||||||
# cert-manager's HTTP-01 solver, which runs only while a certificate
|
|
||||||
# renews: Let's Encrypt and cert-manager's own self check reach it on 8089
|
|
||||||
# through Envoy. The policies above let Envoy reach the app's port only,
|
|
||||||
# which left the solver unreachable (found 2026-10-26, when ynab's renewal
|
|
||||||
# hung).
|
|
||||||
apiVersion: networking.k8s.io/v1
|
|
||||||
kind: NetworkPolicy
|
|
||||||
metadata:
|
|
||||||
name: acme-http01-solver
|
|
||||||
spec:
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
acme.cert-manager.io/http01-solver: "true"
|
|
||||||
policyTypes:
|
|
||||||
- Ingress
|
|
||||||
ingress:
|
|
||||||
- from:
|
|
||||||
- namespaceSelector:
|
|
||||||
matchLabels:
|
|
||||||
kubernetes.io/metadata.name: envoy-gateway-system
|
|
||||||
podSelector:
|
|
||||||
matchLabels:
|
|
||||||
app.kubernetes.io/name: envoy
|
|
||||||
ports:
|
|
||||||
- port: 8089
|
|
||||||
@@ -27,7 +27,7 @@ spec:
|
|||||||
- mountPath: /target
|
- mountPath: /target
|
||||||
name: plugins
|
name: plugins
|
||||||
configuration:
|
configuration:
|
||||||
# Garage on the NAS (nas/garage). Until 2026-10-26 this was MinIO on
|
# Garage on the NAS (nas/garage). Until 2026-10-25 this was MinIO on
|
||||||
# the same NAS; the bucket was copied over with rclone, so the
|
# the same NAS; the bucket was copied over with rclone, so the
|
||||||
# existing backups and kopia repositories carried on.
|
# existing backups and kopia repositories carried on.
|
||||||
backupStorageLocation:
|
backupStorageLocation:
|
||||||
|
|||||||
Reference in new issue
Block a user