Allow k8s edge health checks on arrstack hosts #532
Reference in New Issue
Block a user
Delete Branch "benvin/allow-k8s-edge-healthchecks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The Kubernetes-hosted haproxy edge probes the arr/nzbget backends on
/consul/health, but its traffic arrives SNATed from the node ranges rather than the DMZ edge, so nginx returns 403 and every backend health-checks down.198.18.21.0/24(2.5gbe physical),198.18.15.0/24and198.18.19.0/24(node loopbacks) on thearrstack_web_healthchecklocation.198.18.24.0/24so the existing DMZ edge stays healthy through cutover.