Dominik created FLINK-39667:
-------------------------------
Summary: NGINX Ingress Retirement
Key: FLINK-39667
URL: https://issues.apache.org/jira/browse/FLINK-39667
Project: Flink
Issue Type: Improvement
Components: Kubernetes Operator
Reporter: Dominik
Hi everyone,
the Flink Kubernetes Operator currently relies on Kubernetes Ingress resources
when exposing the Flink Web UI. With the classic Ingress API gradually being
phased out (see the official Kubernetes announcement:
[https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement]) in favour of
the Kubernetes Gateway API (HTTPRoute, TLSRoute, etc.), I was wondering if
there are any plans to support these newer resources.
I couldn’t find any existing discussions or issues around Gateway API support
in the operator (apologies if I missed something).
At the moment, in plain Kubernetes or Gateway API–based environments, users are
still limited to Ingress for exposing the Flink UI. Are there any plans to add
support for Gateway API resources (such as HTTPRoute) as an alternative to
Ingress?
This would be especially useful for environments that are moving away from
Ingress controllers like NGINX and standardizing on Gateway API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
