# 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.
#
# WHY AN OVERLAY AND NOT A CHANGE TO ci/bentopdf/test-values.yaml, which is
# what the pilot did for cyberchef: the install-test runs exactly ONE
# configuration per chart, and the two modes are mutually exclusive. cyberchef
# already pays that price and gives the install-test its HTTPRoute against the
# real Gateway-API CRDs. Spending it a second time here would drop this chart's
# Ingress from the install-test for a schema this repository now exercises
# anyway. So the install keeps testing the Ingress; the route is held at render
# level, which is where its two silent failure modes live.
#
# ingress.enabled: false is not optional here. The two modes are mutually
# exclusive and the chart aborts its own render when both are true, so an
# overlay that only switched httpRoute on would turn this test red.
#
# ingress.domain comes from ci/bentopdf/test-values.yaml, which this overlay
# sits on top of - httpRoute.hostnames is left empty on purpose, so the
# fallback to ingress.domain is what the test exercises.
ingress:
  enabled: false
httpRoute:
  enabled: true
  parentRefs:
    - name: public
      namespace: gateway
      sectionName: https