Simen Lilleeng

Hi! I reproduced this issue with version 1.8.1 of the fdb-kubernetes-operator, see the operator logs in the drop down. **Setup** ``` Spec: Database Configuration: Logs: 5 Proxies: 3 redundancy_mode: triple...

**Idea**: Add an option to provide a list of three availability zones (or 'data halls') in the cluster configuration. And also a corresponding label key. The availability zone is often...

> Are you thinking of a topology where there is a single Kubernetes cluster that spans an entire region? Would you be using the hostname as the lower-order fault domain...

> That issue probably happens for clients outside of the FDB Pods? I believe the issue is that the client cannot write to the mounted cluster file from the ConfigMap....

Yes 👍 I'm thinking of reusing the checks from [ReplaceMisconfiguredProcessGroups](https://github.com/FoundationDB/fdb-kubernetes-operator/blob/e2e34fe3b2899e3409949ccf9b7b0c2c7784c39a/internal/replacements/replacements.go#L42) in [getPodsToUpdate](https://github.com/FoundationDB/fdb-kubernetes-operator/blob/e2e34fe3b2899e3409949ccf9b7b0c2c7784c39a/controllers/update_pods.go#L160). Does that seem sound?

Hi @johscheuer, sorry, I got caught up with other things. I've put up a draft: https://github.com/FoundationDB/fdb-kubernetes-operator/pull/1954