Johannes Scheuermann

The change to the `ProcessConfigs` might be a good choice for the conversion: https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1047

I would propose to implement this as a finalizer and once the FDBBackup resource is deleted the deletion logic will be triggered. We should add a new setting like `deleteOnRemoval`...

It's interessing that the coordinator IPs are not part of the `addresses` in the process group status. Do you know what exactly has happened to the cluster?

I created a follow up issue for this: https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1351 once we implement this we can detect coordinators even if the IP is missing in the ProcessGroup status. I'm going to...

Another approach could be to check in this loop: https://github.com/FoundationDB/fdb-kubernetes-operator/blob/main/controllers/bounce_processes.go#L60-L66 if we have processes that are not version compatible and add them directly to the `addresses` slices. As a safeguard...

We solved this in another issue.

Another occurrence of this behaviour: https://github.com/FoundationDB/fdb-kubernetes-operator/runs/6998769161?check_suite_focus=true

The user could still add it "manually" on the according removal list.

Since https://github.com/helm/charts is not maintained anymore it seems like https://artifacthub.io is the right place + https://operatorhub.io. I think it makes sense to publish the operator on these platforms to make...

I think those are related: https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1240 Could you try adding the port to your configuration and see if that works.