[
https://issues.apache.org/jira/browse/FLINK-26344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gyula Fora resolved FLINK-26344.
--------------------------------
Resolution: Fixed
As a side effect this was also fixed by:
38c366de0d8fa11751051eadbddcf19cb1f31e8f
> 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
> Assignee: Nicholas Jiang
> 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)
