mirror of
https://gitlab.kube.huskypup.net/Scooby/Homelabv4.git
synced 2026-08-21 05:26:49 +00:00
Scooby HuskyandClaude Sonnet 5
c8643ca025
Every other major namespace (gitlab, vault, argocd, nextcloud, etc.) has its own 3-replica netbird-router deployment auto-provisioned from an NBRoutingPeer CR; crowdsec never got one since it never previously needed mesh connectivity. Without it, crowdsec pods had no dedicated mesh routing path, causing intermittent connection resets/hangs reaching the VPS proxy used to route around CrowdSec's WAF block on home's public IP. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
25 lines
1.0 KiB
YAML
25 lines
1.0 KiB
YAML
# Dedicated Netbird mesh router for the crowdsec namespace.
|
|
#
|
|
# Found missing 2026-08-17 while debugging why CrowdSec LAPI couldn't reach
|
|
# api.crowdsec.net through the VPS proxy workaround (home's public IP is
|
|
# WAF-blocked by CrowdSec's own API - see values.yaml HTTPS_PROXY comment).
|
|
# Every other major namespace (gitlab, vault, argocd, nextcloud, etc.) has
|
|
# its own 3-replica netbird-router deployment, auto-provisioned by the
|
|
# netbird-operator from an NBRoutingPeer CR - crowdsec never got one because
|
|
# it never previously needed mesh connectivity. Without it, crowdsec pods'
|
|
# mesh-bound traffic had no reliable dedicated path, causing intermittent
|
|
# connection resets/hangs to the VPS.
|
|
#
|
|
# None of the other 10 NBRoutingPeer CRs are tracked in git either (all
|
|
# created out-of-band) - this is the first one committed, to avoid it being
|
|
# similarly undiscoverable next time.
|
|
apiVersion: netbird.io/v1
|
|
kind: NBRoutingPeer
|
|
metadata:
|
|
name: router
|
|
namespace: crowdsec
|
|
labels:
|
|
app.kubernetes.io/name: netbird-router
|
|
spec:
|
|
resources: {}
|