@johscheuer When I tried to upgrade fdbcluster from 6.2 to 6.3, I found there is some time that fdb is in unavailable status( around 20 minutes), I think during that time fdb pods are copying binaries files and redistributing data, right? But our customer won’t want to stop their workload during upgrade, is it possible for no downtime during fdb upgrade (from 6.2 to 6.3) ? Thanks!
How is this related to the operator upgrade from 0.48 to 1.4.1? Could you please create an issue in GitHub providing all required information like cluster configuration, logs, operator version, FDB version etc., It’s not expected that a cluster get’s unavailable during an upgrade.