williamp/helm-gitea
1
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 18 Wiki Activity

feat(new): gateway support #119

Merged
williamp merged 1 commits from feat-gateway-api into main 2026-07-04 16:34:14 +00:00
Conversation 0 Commits 1 Files Changed 9
+286
williamp commented 2026-07-04 16:23:14 +00:00
Owner
Copy Link
Copy Source

Description of the change

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 support 2026-07-04 16:24:39 +00:00
williamp changed title from Gateway API support to feat(new): Gateway API support 2026-07-04 16:26:17 +00:00
williamp changed title from feat(new): Gateway API support to feat(new): gateway support 2026-07-04 16:27:40 +00:00
williamp added 1 commit 2026-07-04 16:30:44 +00:00
feat(new): gateway api support
check-and-test / check-and-test (pull_request) Successful in 39s
Details
84349e6385
williamp force-pushed feat-gateway-api from 9d9ea09afb to 84349e6385 2026-07-04 16:30:44 +00:00 Compare
williamp merged commit c75355499d into main 2026-07-04 16:34:14 +00:00
williamp deleted branch feat-gateway-api 2026-07-04 16:34:15 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
renovate-bot (Renovate Bot) williamp (William Peebles)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: williamp/helm-gitea#119
Delete Branch "feat-gateway-api"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?