[Feature]: Adding Kubernetes GatewayAPI support for the JFrog Platform Helm Chart

[localleon]

The current JFrog Platform Helm chart supports Kubernetes Ingress but does not offer a way to fully disable Ingress resources when using the Kubernetes Gateway API. Since Gateway API is becoming the new standard across Kubernetes distributions and service meshes, the chart should provide native support for defining a Gateway with Listeners (HTTP + TLS) and corresponding HTTPRoute resources.

Introducing Gateway API support—along with a toggle to disable Ingress—would align the chart with modern Kubernetes networking practices and improve compatibility with service meshes and managed controllers.

Expected Use-Case

• Deployments where Ingress is deprecated, unavailable, or replaced by Gateway API.
• Clusters using service meshes or managed gateways (e.g., Istio, Linkerd, GKE Gateway Controller).

Need to configure:

• A Gateway with multiple listeners (e.g., HTTP and HTTPS).
• HTTPRoute resources routing to JFrog Platform services.
• TLS termination at the Gateway level.
• Users who want routing exclusively managed via Gateway API instead of Ingress resources.

References:

• https://gateway-api.sigs.k8s.io/
• https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/