Repository navigation
Commit 7e206e2
authored
fix(keycloak): point HTTPRoute backends at the service port (#3235)
## Summary
With `gateway-enabled: "true"`, every Keycloak hostname answers 503 from
envoy. The `keycloak-http` Service exposes a single port, 8080:
```yaml
ports:
- name: http
port: 8080
```
but all three HTTPRoute backendRefs in
`packages/system/keycloak/templates/httproute.yaml` reference `port:
80`. Gateway API resolves a backendRef against the Service's declared
ports, so no backend resolves and the route serves 503. The Ingress
template is unaffected because it references the port by name (`http`).
Observed live on the freedom dev cluster: all Keycloak hosts returned
503 via the Gateway; hand-patching the route's backend port to 8080
restored service.
## Change
Point the three backendRefs (public route, its no-adminHost variant, and
the admin route) at port 8080.
Verified with `helm template -s templates/httproute.yaml` (with and
without `ingress.adminHost`): both routes render with `port: 8080`.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Bug Fixes**
* Updated Keycloak HTTP routing so both the main and admin routes
forward traffic to the correct backend service port (from 80 to 8080),
improving reliability and access.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->1 file changed
Lines changed: 3 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
36 | 36 | | |
37 | 37 | | |
38 | 38 | | |
39 | | - | |
| 39 | + | |
40 | 40 | | |
41 | 41 | | |
42 | 42 | | |
43 | | - | |
| 43 | + | |
44 | 44 | | |
45 | 45 | | |
46 | 46 | | |
| |||
62 | 62 | | |
63 | 63 | | |
64 | 64 | | |
65 | | - | |
| 65 | + | |
66 | 66 | | |
67 | 67 | | |
0 commit comments