[FLINK-23507] The node IP obtained in NodePort mode is a VIP

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.13.0, 1.13.1
• Fix Version/s: 1.14.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available

Release Note

When using "kubernetes.rest-service.exposed.type=NodePort", connection string for Rest gateway is now correctly constructed in form of "<nodeIp>:<nodePort>" instead of "<kubernetesApiServerUrl>:<nodePort>". This may be a breaking change for some users.

This also introduces a new config option "kubernetes.rest-service.exposed.node-port-address-type" that lets you select "<nodeIp>" from a desired range.

• Assignee: David Morávek
• Reporter: john
• Created: 27/Jul/21 03:37
• Updated: 15/Feb/22 03:51
• Resolved: 13/Aug/21 14:44

Description

When the three masters of k8s turn on the load balancing mode, when the job is submitted to the k8s cluster and the parameter -Dkubernetes.rest-service.exposed.type=NodePort is used, the web ui address of the job obtained at this time is Get the address of the k8s master, but this address is a VIP. VIP does not belong to the k8s cluster, so it cannot be accessed. The node ip we should get is the IP of any machine in the k8s cluster.
like this：

Issue Links

• fixes: FLINK-16601 Correct the way to get Endpoint address for NodePort rest Service
• is duplicated by: FLINK-23043 Wrong master address displayed when run application in native K8s with -Dkubernetes.rest-service.exposed.type=NodePort
• relates to: FLINK-22975 Specify port or range for k8s service
• links to: GitHub Pull Request #16720