Description of problem (please be detailed as possible and provide log
Support to have at least 2 pods per noobaa component (endpoint, core and db). Because K8S spinning a new pod could last up to 10 minutes and those 10 minutes means with a whole object storage downtime (PUT and GET requests).
4.6 is at dev freeze, as an RFE it should move to 4.7
@nimrod is the ask in this BZ different than Bug 1874243 - [RFE] Noobaa resources are impacted with a downtime during admin operations, such as upgrade, due to no HA for noobaa-core and noobaa-db
In its core, the solution would be the same, the other bug talks about admin ops, this one about failure. But the same solution would apply.