Hi! The cluster-id for each FlinkDeployment is simply the name of the deployment. So they are all different in a given namespace. (In other words they are not fixed as your question suggests but set automatically)
So there should be no problem sharing the ZK cluster . Cheers Gyula On Thu, 21 Sep 2023 at 03:46, Brian King <bk...@wikimedia.org> wrote: > Hello Flink Users! > > We're attempting to deploy a Flink application cluster on Kubernetes, > using the Flink Operator and Zookeeper for HA. > > We're using Flink 1.16 and I have a question about some of the Zookeeper > configuration[0]: > > "high-availability.zookeeper.path.root" is described as "The *root > ZooKeeper node*, under which all cluster nodes are placed" > > "high-availability.cluster-id" , which says "important: customize per > cluster." But it also says "you should not set this value manually when > running on [...] native Kubernetes [...]in those cases a cluster-id is > [...] automatically generated." > > Our design calls for multiple Flink application clusters managed by the > same Flink Operator, and using the same Zookeeper quorum for each Flink > Application cluster. Will the Flink Operator be able to handle this, or > will the different clusters collide due to the fixed > "high-availability.cluster-id" value? Is it possible to avoid this by > setting a unique "high-availability.zookeeper.path.root" for each > application cluster? > > Thanks for your time. I'm new to Flink, so I apologize if I did not > explain myself clearly. Please let me know if you need additional > information. > > Best, > > Brian King > SRE, Data Platform/Search Platform > Wikimedia Foundation > IRC: inflatador > > [0] > https://nightlies.apache.org/flink/flink-docs-release-1.16/docs/deployment/ha/zookeeper_ha/#configuration > > >
