You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Nicholas Jiang (Jira)" <ji...@apache.org> on 2022/02/24 04:56:00 UTC

[jira] [Commented] (FLINK-26344) waitForClusterShutdown does not work correctly in Flink Kubernetes operator

    [ https://issues.apache.org/jira/browse/FLINK-26344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497172#comment-17497172 ] 

Nicholas Jiang commented on FLINK-26344:
----------------------------------------

[~wangyang0918], I would like to fix this bug above mentioned. Could you please assign this ticket to me?

> waitForClusterShutdown does not work correctly in Flink Kubernetes operator 
> ----------------------------------------------------------------------------
>
>                 Key: FLINK-26344
>                 URL: https://issues.apache.org/jira/browse/FLINK-26344
>             Project: Flink
>          Issue Type: Bug
>          Components: Kubernetes Operator
>            Reporter: Yang Wang
>            Priority: Major
>
>  
> {code:java}
> Fabric8FlinkKubeClient flinkKubeClient =
>         new Fabric8FlinkKubeClient(
>                 conf, kubernetesClient, Executors.newSingleThreadExecutor()); {code}
>  
> {{Fabric8FlinkKubeClient}} expects an namespaced Kubernetes client. If we create FlinkDeployment is a different namespace with K8s operator, {{FlinkService#waitForClusterShutdown()}} will not work.
>  
> We could directly use the Kubernetes client to do the existence check for deployment.
> {code:java}
> kubernetesClient.apps().deployments().inNamespace(namespace).withName(clusterId).get() == null{code}



--
This message was sent by Atlassian Jira
(v8.20.1#820001)