Adds support for the Gateway API, specifically creating a HTTPRoute object equivalent to the Ingress object
Benefits
Gateway API is becoming the new standard for ingress management in Kubernetes, while Ingress is on it's way to becoming deprecated in later k8s releases. While it's more complicated compared to the existing Ingress API, it provides better control and cross-namespace management between the application and the ingress controller.
Possible drawbacks
It is generally not advised to have both Ingress and HTTPRoute objects at the same time, therefore I have disallowed both to exist at the same time in the values.
Additional information
The user is expected to already have created the Gateway object prior to chart installation, they could also add it in the extraDeploy section, or create their own template if this chart is being imported as a subchart.
Checklist
Parameters are documented in the values.yaml and added to the README.md using readme-generator-for-helm
Helm templating unittests are added (required when changing anything in templates folder)
All added template resources MUST render a namespace in metadata
<!--
Before you open the request please review the following guidelines and tips to help it be more easily integrated:
- Describe the scope of your change - i.e. what the change does.
- Describe any known limitations with your change.
- Please run any tests or examples that can exercise your modified code.
Thank you for contributing! We will try to review, test and integrate the change as soon as we can.
-->
### Description of the change
Adds support for the [Gateway API](https://gateway-api.sigs.k8s.io/docs/introduction/), specifically creating a `HTTPRoute` object equivalent to the `Ingress` object
### Benefits
Gateway API is becoming the new standard for ingress management in Kubernetes, while Ingress is on it's way to becoming deprecated in later k8s releases. While it's more complicated compared to the existing Ingress API, it provides better control and cross-namespace management between the application and the ingress controller.
### Possible drawbacks
It is generally not advised to have both `Ingress` and `HTTPRoute` objects at the same time, therefore I have disallowed both to exist at the same time in the values.
### Additional information
The user is expected to already have created the `Gateway` object prior to chart installation, they could also add it in the `extraDeploy` section, or create their own template if this chart is being imported as a subchart.
### Checklist
<!-- [Place an '[X]' (no spaces) in all applicable fields. Please remove unrelated fields.] -->
- [X] Parameters are documented in the `values.yaml` and added to the `README.md` using [readme-generator-for-helm](https://github.com/bitnami-labs/readme-generator-for-helm)
- [X] Helm templating unittests are added (required when changing anything in `templates` folder)
- [X] All added template resources MUST render a namespace in metadata
williamp
changed title from feat: Gateway API support, in lieu of Ingress to Gateway API support2026-07-04 16:24:39 +00:00
williamp
changed title from Gateway API support to feat(new): Gateway API support2026-07-04 16:26:17 +00:00
williamp
changed title from feat(new): Gateway API support to feat(new): gateway support2026-07-04 16:27:40 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Description of the change
Adds support for the Gateway API, specifically creating a
HTTPRouteobject equivalent to theIngressobjectBenefits
Gateway API is becoming the new standard for ingress management in Kubernetes, while Ingress is on it's way to becoming deprecated in later k8s releases. While it's more complicated compared to the existing Ingress API, it provides better control and cross-namespace management between the application and the ingress controller.
Possible drawbacks
It is generally not advised to have both
IngressandHTTPRouteobjects at the same time, therefore I have disallowed both to exist at the same time in the values.Additional information
The user is expected to already have created the
Gatewayobject prior to chart installation, they could also add it in theextraDeploysection, or create their own template if this chart is being imported as a subchart.Checklist
values.yamland added to theREADME.mdusing readme-generator-for-helmtemplatesfolder)feat: Gateway API support, in lieu of Ingressto Gateway API supportGateway API supportto feat(new): Gateway API supportfeat(new): Gateway API supportto feat(new): gateway support9d9ea09afbto84349e6385actions referenced this pull request2026-07-04 16:34:23 +00:00