Gateway API Support

[Nephdz]

Gateway API Support is missing.

The Gateway API is becoming the standard for traffic routing in Kubernetes. Adding this integration would align Dify Helm charts with modern Kubernetes networking practices. It would also simplify deployments in environments that already use Gateway API for other services.

[BorisPolonsky]

Thanks for raising this request - we are aware of the fact that Gateway API is becoming the standard and its value in North‑South traffic, though we haven't prioritized native support for now for some reasons:

Based on our observations, the built‑in Ingress provided in the Helm chart is rarely used in real‑world deployments, as external traffic routing (either by Gateway API, Service Mesh such as Istio Gateway, or legacy Ingress) is typically deployed and managed separately by cluster administrators, rather than by application maintainers. For some advanced traffic routing features, the actual implementation varies among ecosystems, hence managing them separately is more practical than to test on each of the ecosystem (and the corresponding infrastructure that we might not have access to) within the chart.

Still, we are open to accepting PRs that implement built-in Gateway API support for North‑South traffic routing, so long as they maintain backward compatibility for existing users who rely on Ingress, Istio, or other solutions and the simplicity of the chart.

Thanks for your insights and let's keep up the pace with the evolution of the community together.

[Nephdz]

Thanks, I will work on a PR for this as I'm getting through switching things over to Gateway API