HOMELAB-510: fix(gateway): remove Harbor HTTPRoute — use direct LB #109

Merged
aaron merged 1 commit from plane/HOMELAB-510-remove-harbor-route into live 2026-03-31 05:20:32 +00:00
Owner

INCIDENT

Harbor's HTTPRoute via Cilium Gateway creates a redirect loop. Harbor already has its own LoadBalancer with TLS. Remove the HTTPRoute and route traffic through the LB IP directly.

DNS (ControlD) needs updating: harbor.aaron.reynoza.org10.10.10.223 (LB IP).

## INCIDENT Harbor's HTTPRoute via Cilium Gateway creates a redirect loop. Harbor already has its own LoadBalancer with TLS. Remove the HTTPRoute and route traffic through the LB IP directly. DNS (ControlD) needs updating: `harbor.aaron.reynoza.org` → `10.10.10.223` (LB IP).
HOMELAB-510: fix(gateway): remove Harbor HTTPRoute — use direct LB instead
Some checks failed
0/0 projects applied successfully.
CI Review / pr-title (pull_request) Has been cancelled
CI Review / helm-validate (pull_request) Has been cancelled
CI Review / ai-review (pull_request) Has been cancelled
Lint & Validate / terraform-validate (pull_request) Has been cancelled
Lint & Validate / yaml-lint (pull_request) Has been cancelled
Lint & Validate / shellcheck (pull_request) Has been cancelled
52d5bbc195
Harbor has its own LoadBalancer service (10.10.10.223) with TLS
configured. The HTTPRoute through Cilium Gateway creates a redirect
loop because the Gateway terminates TLS and forwards plain HTTP to
Harbor's port 80, which redirects back to HTTPS.

Harbor needs TLS on its own service for kubelet image pulls, so we
can't disable Harbor's TLS. The simplest fix is to remove the
HTTPRoute and let all traffic go through Harbor's LoadBalancer IP
directly. ControlD DNS should resolve harbor.aaron.reynoza.org to
10.10.10.223 (the LB IP) instead of 10.10.10.228 (the Gateway IP).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
aaron merged commit 35e2c3123c into live 2026-03-31 05:20:32 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aaron/infra-core!109
No description provided.