Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

I think we have no concrete reason to always override the "REST_SERVICE_EXPOSED_TYPE" to "ClusterIP". It was introduced to fix the default value for releases before 1.15. And I believe we need to respect the user configured values. Best, Yang Vignesh Kumar Kathiresan 于2022年9月3日周六 05:07写道： > Jac

Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

Jacob, Thanks, I checked it out and didn't work. The config overriding to ClusterIP part

Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

I remember testing the operator with the rest service exposed as NodePort. NodePort requires rbac.nodeRoules.create: true (default is false) in values.yaml. Maybe you missed that? https://github.com/apache/flink-kubernetes-operator/blob/release-1.1/helm/flink-kubernetes-operator/values.yaml#L34-L3

Re: [E] Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

Hi Yang, Yeah, I gathered that from the operator code soon after posting. I am using the aws alb ingress class [1]. There under considerations it is mentioned if the alb target type is "instance" which is the default traffic mode, the kubernetes service type has to be nodeport or loadbalancer. Al

Re: Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

I am afraid the current flink-kubernetes-operator always overrides the "REST_SERVICE_EXPOSED_TYPE" to "ClusterIP". Could you please share why the ingress[1] could not meet your requirements? Compared with NodePort, I think it is a more graceful implementation. [1]. https://nightlies.apache.org/fli

Kubernetes operator expose UI rest service as NodePort instead of default clusterIP

Hello Flink community, Need some help with "flink kubernetes operator" based cluster setup. My flink cluster is set up using the flink-kubernetes-operator in AWS EKS. The required resources(deployments, pods, services, configmaps etc) are created as expected. But the service "*-rest" is created a