[jira] [Updated] (FLINK-27809) Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode

2024-03-11 Thread lincoln lee (Jira)


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

lincoln lee updated FLINK-27809:

Fix Version/s: (was: 1.19.0)

> Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode
> -
>
> Key: FLINK-27809
> URL: https://issues.apache.org/jira/browse/FLINK-27809
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Configuration
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.20.0
>
>
> The description for KubernetesConfigOptions#CLUSTER_ID states that the client 
> generates this automatically if it isn't set. This is technically correct, 
> because the client is not involved in the deployment for standalone clusters, 
> but to users this sounds like it is optional in general, while it must be set 
> (to an ideally unique value) in standalone mode.



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


[jira] [Updated] (FLINK-27809) Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode

2024-03-11 Thread lincoln lee (Jira)


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

lincoln lee updated FLINK-27809:

Fix Version/s: 1.20.0

> Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode
> -
>
> Key: FLINK-27809
> URL: https://issues.apache.org/jira/browse/FLINK-27809
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Configuration
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.19.0, 1.20.0
>
>
> The description for KubernetesConfigOptions#CLUSTER_ID states that the client 
> generates this automatically if it isn't set. This is technically correct, 
> because the client is not involved in the deployment for standalone clusters, 
> but to users this sounds like it is optional in general, while it must be set 
> (to an ideally unique value) in standalone mode.



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


[jira] [Updated] (FLINK-27809) Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode

2023-10-13 Thread Jing Ge (Jira)


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

Jing Ge updated FLINK-27809:

Fix Version/s: 1.19.0
   (was: 1.18.0)

> Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode
> -
>
> Key: FLINK-27809
> URL: https://issues.apache.org/jira/browse/FLINK-27809
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Configuration
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.19.0
>
>
> The description for KubernetesConfigOptions#CLUSTER_ID states that the client 
> generates this automatically if it isn't set. This is technically correct, 
> because the client is not involved in the deployment for standalone clusters, 
> but to users this sounds like it is optional in general, while it must be set 
> (to an ideally unique value) in standalone mode.



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


[jira] [Updated] (FLINK-27809) Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode

2023-03-23 Thread Xintong Song (Jira)


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

Xintong Song updated FLINK-27809:
-
Fix Version/s: 1.18.0
   (was: 1.17.0)

> Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode
> -
>
> Key: FLINK-27809
> URL: https://issues.apache.org/jira/browse/FLINK-27809
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Configuration
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.18.0
>
>
> The description for KubernetesConfigOptions#CLUSTER_ID states that the client 
> generates this automatically if it isn't set. This is technically correct, 
> because the client is not involved in the deployment for standalone clusters, 
> but to users this sounds like it is optional in general, while it must be set 
> (to an ideally unique value) in standalone mode.



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


[jira] [Updated] (FLINK-27809) Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode

2022-08-22 Thread Xingbo Huang (Jira)


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

Xingbo Huang updated FLINK-27809:
-
Fix Version/s: 1.17.0
   (was: 1.16.0)

> Clarify that cluster-id is mandatory for Kubernetes HA in standalone mode
> -
>
> Key: FLINK-27809
> URL: https://issues.apache.org/jira/browse/FLINK-27809
> Project: Flink
>  Issue Type: Improvement
>  Components: Deployment / Kubernetes, Runtime / Configuration
>Reporter: Chesnay Schepler
>Priority: Major
> Fix For: 1.17.0
>
>
> The description for KubernetesConfigOptions#CLUSTER_ID states that the client 
> generates this automatically if it isn't set. This is technically correct, 
> because the client is not involved in the deployment for standalone clusters, 
> but to users this sounds like it is optional in general, while it must be set 
> (to an ideally unique value) in standalone mode.



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