Merge pull request 'feat(keycloak): one hostname per realm, in both routing modes' (#125) from feat/keycloak-realm-hosts into main

ci/httproute/keycloak.yaml

@@ -30,11 +30,29 @@
 #     parentRefs fall back to httpRoute.parentRefs below - the empty-admin
 #     branch, which is the one an installation hits unless it wants an
 #     internal Gateway.
-#   - both routes' backendRef is checked against the serving Service of the
-#     same render. Both point at the SAME Service, by PORT NUMBER
+#   - every route's backendRef is checked against the serving Service of the
+#     same render. They all point at the SAME Service, by PORT NUMBER
 #     (keycloak.ports.http) rather than by the name "http" the Ingress uses,
 #     because backendRefs takes a PortNumber - so this overlay is what holds
 #     that number against the Service's.
+#   - THE TWO REALM ROUTES (Gitea #122), which come from keycloak.realmHosts in
+#     the fixture rather than from this file. Nothing is repeated here on
+#     purpose: the fixture installs them as Ingress objects and this overlay
+#     turns the same two entries into HTTPRoutes, so one definition covers both
+#     modes and the two halves cannot drift into describing different hostnames.
+#     What the routes add to the two above is a SECOND RULE SHAPE - an Exact
+#     match on / carrying a RequestRedirect filter and no backendRefs at all.
+#     That rule is reported as "not checked" by this test, correctly and by
+#     design: a filter-only rule has no backend to resolve. The assertion it
+#     does earn is on its sibling rule, the PathPrefix one that points at the
+#     Service. The prefix/redirect pairing check of #118 does NOT fire for these
+#     routes and must not: it is scoped to rules that STRIP a prefix with a
+#     ReplacePrefixMatch rewrite, and these strip nothing - they redirect the
+#     bare root of a hostname that serves one realm.
+#     The entries also cover the two Ingress-mode forms (one with a
+#     clusterIssuer, one without) and what this test holds about them is their
+#     INERTNESS: neither tlsSecretName nor clusterIssuer nor the per-entry
+#     annotation may appear anywhere in a rendered route.
 #
 # NOT covered here, and it cannot be: that either hostname answers. No Gateway
 # controller runs in CI, no route reaches "Accepted: True", and the