You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2020/12/08 06:40:10 UTC
[jira] [Updated] (FLINK-18986) KubernetesSessionCli creates
RestClusterClient for detached deployments
[ https://issues.apache.org/jira/browse/FLINK-18986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Metzger updated FLINK-18986:
-----------------------------------
Fix Version/s: (was: 1.12.0)
1.13.0
> KubernetesSessionCli creates RestClusterClient for detached deployments
> -----------------------------------------------------------------------
>
> Key: FLINK-18986
> URL: https://issues.apache.org/jira/browse/FLINK-18986
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Kubernetes
> Affects Versions: 1.11.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Priority: Minor
> Labels: pull-request-available, usability
> Fix For: 1.13.0
>
>
> The {{KubernetesSessionCli}} creates a {{ClusterClient}} for retrieving the {{clusterId}} if the cluster was just started.
> However, this {{clusterId}} is only used in attached executions.
> For detached deployments where {{kubernetes.rest-service.exposed.type}} is set to {{ClusterIP}} this results in unnecessary error messages about the {{RestClusterClient}} not being able to be created.
> Given that there is no need to create the client in this situation, we should skip this step.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)