[
https://issues.apache.org/jira/browse/FLINK-23507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Morávek updated FLINK-23507:
----------------------------------
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.
was:
When using "kubernetes.rest-service.exposed.type=NodePort", connection string
for Rest gateway is now correctly constructed as <nodeIp>:<nodePort> insted 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.
> The node IP obtained in NodePort mode is a VIP
> ----------------------------------------------
>
> Key: FLINK-23507
> URL: https://issues.apache.org/jira/browse/FLINK-23507
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.13.0, 1.13.1
> Reporter: john
> Assignee: David Morávek
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.14.0
>
> Attachments: image-2021-07-27-11-36-56-280.png
>
>
> 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：
> !image-2021-07-27-11-36-56-280.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
