You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2021/02/16 16:18:00 UTC

[jira] [Created] (FLINK-21382) Standalone K8s documentation does not explain usage of standby JobManagers

Till Rohrmann created FLINK-21382:
-------------------------------------

             Summary: 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


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)