mirror of
https://gitlab.kube.huskypup.net/Scooby/Homelabv4.git
synced 2026-08-23 12:56:46 +00:00
Scooby HuskyandClaude Sonnet 5
04fa80ece3
Per the approved plan (jiggly-snacking-iverson.md, 'GitLab True Cross-Site Replication' section) - replacing the git-mirror CronJob with real CNPG streaming replication for pg-gitlab and pg-praefect, reusing the exact pattern already proven for pg-authentik. This commit is network plumbing only, no DB replication yet: - Repoint both CNPG clusters' barmanObjectStore backup target from in-cluster gitlab-minio-svc to VPS MinIO (also becomes the initial seed source for the VPS's replicas in Phase 1c). - New ha-gitlab-postgres/ha-praefect-postgres NodePort Services (bypass CNPG's own -rw Services) on both home and VPS. - New PeerAuthentication with portLevelMtls PERMISSIVE on the replication ports - ambient mesh STRICT default would otherwise reset the VPS/witness's connection before the Postgres TLS handshake starts. - Extended allow-gitlab-access AuthorizationPolicy with a port-scoped rule for the same traffic (no source.namespaces rule can match external, non-mesh peers). - CoreDNS rewrites for pg-gitlab.ha.huskypup.net / pg-praefect.ha.huskypup.net so home's own pods reach the floating hostname locally instead of round-tripping through the WAN forward (no NAT hairpin support). Still needed before Phase 1b/1c: UniFi WAN port-forwards for external ports 61442/61443 -> talos-cp-01:32442/32443, source-restricted to the VPS + witness public IPs (manual, same as the existing 61432 rule). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
52 lines
1.7 KiB
YAML
52 lines
1.7 KiB
YAML
# GitLab cross-site replication (see
|
|
# /home/scooby/.claude/plans/jiggly-snacking-iverson.md) - direct copy of
|
|
# infrastructure/authentik/manifests/ha-postgres-peerauth.yaml's proven
|
|
# fix. The gitlab namespace carries the same ambient-mesh STRICT default
|
|
# as authentik; without this, ztunnel resets the VPS/witness's connection
|
|
# (no mesh identity - they're not in this cluster) before the Postgres
|
|
# TLS handshake can even start, surfacing as "server closed the
|
|
# connection unexpectedly" on the replica side despite the NodePort/
|
|
# firewall path being entirely correct.
|
|
#
|
|
# Scoped to just each CNPG primary pod's ports via portLevelMtls, not the
|
|
# whole namespace - GitLab's own in-mesh east-west traffic (webservice
|
|
# <-> gitaly <-> redis <-> sidekiq <-> praefect) stays STRICT.
|
|
apiVersion: security.istio.io/v1
|
|
kind: PeerAuthentication
|
|
metadata:
|
|
name: allow-ha-gitlab-postgres-replication
|
|
namespace: gitlab
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
cnpg.io/cluster: pg-gitlab
|
|
mtls:
|
|
mode: STRICT
|
|
portLevelMtls:
|
|
"5432":
|
|
mode: PERMISSIVE
|
|
# Floating-hostname port (see ha-postgres-nodeport.yaml) - needs its
|
|
# own entry, ambient's port-level mTLS enforcement is keyed on the
|
|
# port actually dialed (61442), not just the pod's real containerPort
|
|
# (5432) it eventually reaches (confirmed live for the authentik
|
|
# precedent, same mechanism here).
|
|
"61442":
|
|
mode: PERMISSIVE
|
|
---
|
|
apiVersion: security.istio.io/v1
|
|
kind: PeerAuthentication
|
|
metadata:
|
|
name: allow-ha-praefect-postgres-replication
|
|
namespace: gitlab
|
|
spec:
|
|
selector:
|
|
matchLabels:
|
|
cnpg.io/cluster: pg-praefect
|
|
mtls:
|
|
mode: STRICT
|
|
portLevelMtls:
|
|
"5432":
|
|
mode: PERMISSIVE
|
|
"61443":
|
|
mode: PERMISSIVE
|