immich-app/yucca-o11y
1
0
Fork 0
mirror of https://github.com/immich-app/yucca-o11y.git synced 2026-09-30 13:23:23 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix: trust NetBird peer sources on apid/kube-apiserver to cure the elected-router hairpin (#198)

Browse Source 
Signed-off-by: Devin Buhl <devin@buhl.casa>
This commit is contained in:
Devin Buhl
2026-08-13 10:33:03 -04:00
committed by GitHub
parent 6bb5698787
commit 1927887181
6 changed files with 55 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/01-bootstrap-guide.md
+1 -1
View File
@@ -31,7 +31,7 @@ export TF_VAR_env=staging
mise run //deployment/modules/ovh/account:apply
```
2. **NetBird** — the per-environment mesh objects (all named `o11y-<env>-*`): groups and setup keys for the Talos nodes and the in-cluster routing peers, the vRack network route, the mesh-gateway VIP resource and DNS zone, the pod-egress network, and the access policies (`yucca → resource`, `yucca → gateway`, `talos → bootstrap opc`). The Talos module consumes the node setup key and mesh zone from here, so apply NetBird first.
2. **NetBird** — the per-environment mesh objects (all named `o11y-<env>-*`): groups and setup keys for the Talos nodes and the in-cluster routing peers, the vRack network route, the mesh-gateway VIP resource and DNS zone, the pod-egress network, and the access policies (`yucca → resource`, `yucca → talos`, `yucca → gateway`, `talos → bootstrap opc`). The Talos module consumes the node setup key and mesh zone from here, so apply NetBird first.
```bash
mise run //deployment/modules/netbird/cluster:apply