Details
-
Improvement
-
Status: Open
-
Minor
-
Resolution: Unresolved
-
None
-
None
-
None
Description
When deploying Flink on Kubernetes (standalone; application mode; KubernetesHighAvailabilityServices), I would like to configure the name of the ConfigMaps used for leader election via the flink-conf.yaml to make it fully deterministic.
In https://issues.apache.org/jira/browse/FLINK-24038 the number of ConfigMaps is reduced, so that this could potentially be a single configuration option.
Attachments
Issue Links
- is related to
-
FLINK-15816 Limit the maximum length of the value of kubernetes.cluster-id configuration option
- Reopened
-
FLINK-24038 DispatcherResourceManagerComponent fails to deregister application if no leading ResourceManager
- Closed