[jira] [Updated] (FLINK-21382) Standalone K8s documentation does not explain usage of standby JobManagers
[ https://issues.apache.org/jira/browse/FLINK-21382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated FLINK-21382: --- Labels: pull-request-available (was: ) > Standalone K8s documentation does not explain usage of standby JobManagers > -- > > Key: FLINK-21382 > URL: https://issues.apache.org/jira/browse/FLINK-21382 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes, Documentation >Affects Versions: 1.12.1, 1.13.0 >Reporter: Till Rohrmann >Assignee: Yang Wang >Priority: Major > Labels: pull-request-available > Fix For: 1.13.0, 1.12.3 > > > Our [standalone K8s > documentation|https://ci.apache.org/projects/flink/flink-docs-release-1.12/deployment/resource-providers/standalone/kubernetes.html#high-availability-with-standalone-kubernetes] > mentions how to configure K8s HA services. It does not mention that this > only works with a single JobManager. When using standby JobManagers, then the > given deployment yamls won't work because the {{jobmanager.rpc.address}} is > configured to be the {{jobmanager}} service. > Changing the configuration to work is surprisingly difficult because of a > lack of documentation. Moreover, it is quite difficult to pass in custom > configuration values when using a ConfigMap for sharing Flink's > {{flink-conf.yaml}}. The problem is that mounted ConfigMaps are not writable > from a pod perspective. See [this > answer|https://stackoverflow.com/a/66228073/4815083] for how one could > achieve it. > I think we could improve our documentation to explain our users how to > configure a standalone HA cluster with standby JobManagers. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FLINK-21382) Standalone K8s documentation does not explain usage of standby JobManagers
[ https://issues.apache.org/jira/browse/FLINK-21382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yang Wang updated FLINK-21382: -- Fix Version/s: 1.12.3 1.13.0 > Standalone K8s documentation does not explain usage of standby JobManagers > -- > > Key: FLINK-21382 > URL: https://issues.apache.org/jira/browse/FLINK-21382 > Project: Flink > Issue Type: Improvement > Components: Deployment / Kubernetes, Documentation >Affects Versions: 1.12.1, 1.13.0 >Reporter: Till Rohrmann >Assignee: Yang Wang >Priority: Major > Fix For: 1.13.0, 1.12.3 > > > Our [standalone K8s > documentation|https://ci.apache.org/projects/flink/flink-docs-release-1.12/deployment/resource-providers/standalone/kubernetes.html#high-availability-with-standalone-kubernetes] > mentions how to configure K8s HA services. It does not mention that this > only works with a single JobManager. When using standby JobManagers, then the > given deployment yamls won't work because the {{jobmanager.rpc.address}} is > configured to be the {{jobmanager}} service. > Changing the configuration to work is surprisingly difficult because of a > lack of documentation. Moreover, it is quite difficult to pass in custom > configuration values when using a ConfigMap for sharing Flink's > {{flink-conf.yaml}}. The problem is that mounted ConfigMaps are not writable > from a pod perspective. See [this > answer|https://stackoverflow.com/a/66228073/4815083] for how one could > achieve it. > I think we could improve our documentation to explain our users how to > configure a standalone HA cluster with standby JobManagers. -- This message was sent by Atlassian Jira (v8.3.4#803005)