You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yang Wang (Jira)" <ji...@apache.org> on 2022/07/26 01:53:00 UTC

[jira] [Closed] (FLINK-28353) Exclude unschedulable nodes using IP addresses of kubernetes nodes

     [ https://issues.apache.org/jira/browse/FLINK-28353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Yang Wang closed FLINK-28353.
-----------------------------
    Fix Version/s: 1.16.0
         Assignee: Suxing Lee
       Resolution: Fixed

Fixed via:

master: 48acc1c138309df2f72533777d463fd2225e6fba

> Exclude unschedulable nodes using IP addresses of kubernetes nodes
> ------------------------------------------------------------------
>
>                 Key: FLINK-28353
>                 URL: https://issues.apache.org/jira/browse/FLINK-28353
>             Project: Flink
>          Issue Type: Improvement
>          Components: Deployment / Kubernetes
>    Affects Versions: 1.14.4, 1.15.0
>            Reporter: Suxing Lee
>            Assignee: Suxing Lee
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.16.0
>
>
> 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 the IP of any machine in the k8s cluster.
> but client will throw connect refuse exception when the node's schedule status is unschedulable. We should exclude those node IPs to choose web ui address



--
This message was sent by Atlassian Jira
(v8.20.10#820010)