feat: Gateway-API as an alternative to the Ingress in eight charts

Group 1 of the #114 sweep: the charts that render exactly one Ingress object
and set no behaviour-bearing nginx annotation - bentopdf, garage, patchmon,
rallly, searxng, sure, urlaubsverwaltung, voucher-vault.

Each gets the form the pilot (cyberchef, PR #115) fixed and template-chart
carries: an httpRoute block (enabled/parentRefs/hostnames, off by default), a
template rendering ONLY an HTTPRoute with parentRefs - no Gateway, no
gatewayClassName, no Certificate, no implementation-specific policy object -
render aborts on both modes at once (naming both value paths), on an empty
parentRefs and on a missing hostname, empty hostnames meaning [ingress.domain],
a schema entry closed against unknown keys with an open parentRef definition,
and a NOTES.txt that names the active mode and what the mode costs.

Minor, additive, defaults unchanged: `helm template` with each chart's CI
values is byte-identical to origin/main for seven of the eight, and for sure
identical in every rendered value (the diff is two YAML comment lines).

Three findings that were not in the plan, each argued in the file it changes:

  sure derived RAILS_ASSUME_SSL/RAILS_FORCE_SSL from ingress.enabled alone.
  Gateway mode sets that false by construction while TLS is still terminated at
  the Gateway, so both flags would have gone false: insecure cookies, no HSTS,
  http:// links, with a Ready pod and a working UI as the only symptom. They now
  read sure.publishedOverTls (ingress.enabled OR httpRoute.enabled), which is
  ingress.enabled while httpRoute.enabled is false - hence still Minor.

  garage claimed, in its Ingress template and its schema, that nothing outside
  that template reads ingress.domain. The HTTPRoute reads it, so the claim now
  holds only while both modes are off. Corrected rather than left standing.

  garage also depends on an upload limit it does not set: its annotations
  comment tells the operator to set proxy-body-size: "0" because ingress-nginx
  truncates S3 uploads at 1 MB. proxy-body-size has no Gateway-API counterpart,
  so its Gateway-mode NOTES prints that the limit is the Gateway's. README's
  list of affected charts named five and now names garage as a sixth.

clusterIssuer needed no change in any of the eight: its only required() sits
inside the Ingress template behind ingress.enabled, the same no-op the pilot
found. Annotation guidance that stops applying in Gateway mode moved into the
Gateway branch of NOTES.txt for bentopdf (X-Robots-Tag) and searxng
(forward-auth).

CI: one render overlay per chart under ci/httproute/, so the assertion is not
vacuum-green - ci/run-httproute-match-test.sh goes from 4 held assertions over
2 charts to 20 over 10. The install-test fixtures stay in Ingress mode: the
install runs one configuration per chart, cyberchef already pays that price
against the real Gateway-API CRDs, and for garage the Ingress is the only place
its Service port is referenced by NAME.

Not proven, by construction: that traffic flows. No Gateway controller runs in
CI. Not run locally either: k3d, Docker, Trivy.

Part of #114

garage/values.yaml

@@ -421,11 +421,21 @@ ingress:
   # there is nothing to publish. The values exist, built to this repo's
   # convention, so that publishing the endpoint later is a values change.
   #
-  # Guideline 1, checked in both directions: nothing outside the Ingress
-  # template reads ingress.domain (the vhost suffix is its own value,
-  # garage.s3.rootDomain), so switching the Ingress off frees BOTH domain and
-  # clusterIssuer. With it on, both are required and the required() fires in
-  # the template.
+  # Mutually exclusive with httpRoute.enabled below (Gitea #114): with both
+  # true the render aborts, naming both values. Both ship off, so this chart
+  # publishes nothing until asked - in either mode.
+  #
+  # Guideline 1, checked in both directions, and the answer MOVED with #114:
+  # the Ingress template is no longer the only reader of ingress.domain - the
+  # HTTPRoute reads it too, as its single hostname, when httpRoute.hostnames is
+  # empty. So domain is free only while BOTH routing modes are off; with either
+  # one on it is required, and the required() fires in whichever template is
+  # rendering. clusterIssuer is unchanged: it is read only by the Ingress, so
+  # ingress.enabled: false frees it in every case - Gateway mode renders no
+  # Certificate at all.
+  #
+  # Unchanged as well: the vhost suffix is its own value, garage.s3.rootDomain,
+  # and is still deliberately not coupled to ingress.domain.
   enabled: false
   clusterIssuer: null
   domain: null
@@ -434,4 +444,60 @@ ingress:
   # cluster-issuer annotation the chart always sets. An S3 endpoint behind
   # nginx usually wants nginx.ingress.kubernetes.io/proxy-body-size: "0" -
   # without it the controller's 1m default truncates uploads.
+  #
+  # THAT ONE HAS NO COUNTERPART IN GATEWAY MODE. The Gateway API has no
+  # annotation channel and no notion of a body size at all - an upload limit is
+  # implementation-specific policy - so an S3 endpoint published through an
+  # HTTPRoute silently inherits the Gateway's limit, whatever it is. For an
+  # object store that is not a detail: it is where PUTs start failing by size.
+  # The chart does not rebuild it (a policy object would bind it to one
+  # implementation); NOTES.txt prints the warning in that mode and the limit
+  # has to be raised at the Gateway.
   annotations: {}
+
+# Gateway-API alternative to the Ingress above (Gitea #114). Off by default -
+# like the Ingress here, so this chart still publishes nothing unless asked.
+# Exactly one of ingress.enabled and httpRoute.enabled may be true.
+#
+# The chart renders ONLY an HTTPRoute with parentRefs - no Gateway, no
+# gatewayClassName, no Certificate and no implementation-specific policy
+# object. Class and certificate belong to the Gateway and therefore to the
+# platform, which is what keeps this chart independent of whether the cluster
+# runs nginx-gateway-fabric, Cilium, Envoy Gateway or Istio.
+#
+# The Gateway-API CRDs must be installed in the cluster: the chart does not and
+# cannot detect them (.Capabilities.APIVersions is unreliable at template
+# time), so with httpRoute.enabled: true and no CRDs the INSTALL fails.
+#
+# WHAT GETS PUBLISHED IS THE S3 API, in this mode exactly as in Ingress mode:
+# the route points at the Service's s3 port and nothing else. The admin port is
+# deliberately not routed. Read the Ingress comment above before turning either
+# mode on - and read the upload-limit note, which is the one real regression of
+# this mode for an object store.
+httpRoute:
+  enabled: false
+  # The Gateway(s) this route attaches to - a platform object, usually in
+  # another namespace, which must allow this namespace in its listener's
+  # allowedRoutes. One entry per parent, the fields are the Gateway API's
+  # ParentReference (name, and optionally namespace, sectionName, port, group,
+  # kind), passed through unchanged:
+  #
+  #   parentRefs:
+  #     - name: public
+  #       namespace: gateway
+  #       sectionName: https
+  #
+  # REQUIRED while httpRoute.enabled is true - the render aborts on an empty
+  # list, because a route without a parent is created, is valid and routes
+  # nothing, with no event to say so.
+  parentRefs: []
+  # Empty means [ingress.domain], so the hostname has one source of truth. Set
+  # explicitly only to publish under a different or an additional name - which
+  # is how a migration from the Ingress runs: the HTTPRoute takes a second
+  # hostname while the Ingress keeps ingress.domain.
+  #
+  # For vhost-style bucket access this is where the wildcard goes
+  # ("*.s3.example.com" alongside the plain host), together with
+  # garage.s3.rootDomain - the two still have to be set in step, as they do for
+  # the Ingress.
+  hostnames: []