# Render-only overlay for ci/run-httproute-match-test.sh, applied LAST.
#
# Its one job is to put this chart into Gateway mode, because the convention
# ships with httpRoute.enabled: false and the test would otherwise be green
# over nothing. A chart that has an overlay here and still renders no
# HTTPRoute FAILS the test - that is the whole point of the file existing.
#
# THIS CHART IS THE ONE WHERE THE OVERLAY EARNS ITS KEEP TWICE OVER, and the
# reason is in ci/garage/test-values.yaml: that fixture keeps the Ingress ON
# deliberately, so the install-test proves the Service port it names BY NAME
# ("s3") exists. An HTTPRoute cannot make that reference - backendRefs takes a
# PortNumber - so garage is the one chart in the sweep whose route renders a
# port NUMBER out of a VALUE (garage.ports.s3), not a literal. Switching the
# install fixture into Gateway mode would have traded a check that catches a
# renamed port for one that does not, and would have given up garage's only
# Ingress coverage at the same time. Here the number is held instead by this
# test, which fails when a backendRef names a port the same render's Service
# does not expose - exactly the drift the value introduces.
#
# ingress.enabled: false is not optional here. The two modes are mutually
# exclusive and the chart aborts its own render when both are true, and this
# chart's fixture has the Ingress on, so the overlay must switch it off.
#
# ingress.domain comes from ci/garage/test-values.yaml. Note that garage ships
# ingress.enabled: false AND httpRoute.enabled: false, so without this overlay
# the chart renders no route at all - which is correct and is why the overlay
# exists rather than a changed default.
ingress:
  enabled: false
httpRoute:
  enabled: true
  parentRefs:
    - name: public
      namespace: gateway
      sectionName: https