Support for Gateway API (Gateway, HTTPRoute, etc.) as an alternative to Ingress

[Momotoculteur]

Hello team,

The Kubernetes Gateway API is increasingly becoming the new standard for managing incoming traffic, and many platforms are beginning to move away from traditional Ingress resources in favor of Gateway, HTTPRoute, TLSRoute, and others.

Would it be possible to add native support for these resources in the Jenkins Helm Charts?

Describe the problem

Ingress objects are now limited in terms of advanced traffic management, granular rule handling, multi-proxy setups, etc.

The Gateway API provides a more flexible and extensible model and is better integrated with modern controllers (Contour, Istio, GKE Gateway, Envoy Gateway, HAProxy, etc.).

Many other Helm charts already provide either an alternative or a toggle between Ingress and Gateway API.

Solution brainstorm

• Add a gatewayApi configuration block similar to the existing ingress block, for example:

gatewayApi:
  enabled: true
  ...

• Generate the required Gateway, HTTPRoute & others needed manifests when gatewayApi.enabled = true.

Additional context

• Aligns the chart with modern Kubernetes networking standards.
• Provides greater flexibility for users relying on advanced traffic controllers.
• Ensures long-term maintainability as Ingress becomes progressively less favored.

Thank you for your work on this chart!
If helpful, I can also propose a PR once the direction is approved.

[Mart-Kuc]

Hello @Momotoculteur,

From my point of view, it makes sense to add support for the GatewayAPI standard. I can prepare it or feel free to create PR how you've just mentioned