Add Gateway API HTTPRoute support

[Copilot]

Adds Gateway API v1 HTTPRoute as an alternative to the deprecated Ingress resource.

Changes

• New template: templates/httproute.yaml implements Gateway API v1 HTTPRoute spec
  • Supports multiple parent references (Gateways) with full field configuration
  • Supports multiple hostnames including wildcards
  • Supports path, header, and query parameter matching
  • Optional matches field allows catch-all rules
• Configuration: Added httpRoute section to values.yaml (disabled by default)
• Documentation: Updated README template and regenerated with helm-docs

Usage

httpRoute:
  enabled: true
  parentRefs:
    - name: my-gateway
      namespace: gateway-system
  hostnames:
    - semaphore.example.com
  rules:
    - matches:
        - path:
            type: PathPrefix
            value: /api
          headers:
            - type: Exact
              name: X-API-Version
              value: "2.0"

HTTPRoute and Ingress can coexist for gradual migration scenarios.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Support Gateway API HTTPRoute</issue_title>
<issue_description>Since ingress is going to be depreciated, it would be nice if Semaphore chart supported the gateway api for httproute in addition to ingress until it is fully removed.

Thanks</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Support Gateway API HTTPRoute #18

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[mha-cdm]

Hi,

Can we expect this in the upcoming release ?

Many thanks for your efforts