21 lines
1.2 KiB
Markdown
21 lines
1.2 KiB
Markdown
# Traefik
|
||
|
||
The Argo CD Application adopts the existing `traefik` Helm release in
|
||
`default`. `bootstrap/traefik.yaml` is the single chart-version source; the
|
||
values here preserve the cluster's current controller settings and live
|
||
file-provider routes. Its LoadBalancer address is allocated by Kubernetes and
|
||
observed by the MikroTik operator; do not pin it here. Those routes include the staubsauger vacuum, Victron
|
||
NanoPi and WebSocket endpoint, Growatt, and OpenDTU. Do not restore the
|
||
commented/retired routers from the former local configuration.
|
||
|
||
The operator forwards WAN traffic to the dynamically allocated LoadBalancer
|
||
address from MetalLB's `192.168.0.10–49` L2 pool. The separate
|
||
`traefik-funkfeuer` Service also exposes ports 80/443 at `192.168.0.2` for
|
||
direct LAN access and `10.12.4.170` for OLSR access. Those fixed entrypoints
|
||
depend on `arschrock` being online; Traefik replicas may run on the Odroids
|
||
because the additional Service uses cluster-wide endpoint routing.
|
||
|
||
Traefik CRDs and Gateway API CRDs are cluster-wide prerequisites. Keep the
|
||
existing CRDs during adoption and upgrades; they are not safe cleanup targets.
|
||
Application-specific ingress resources remain with their owning application.
|