Bug 1889616 - [RFE] Implement 2 pods per noobaa component (core and db) [NEEDINFO]
Summary: [RFE] Implement 2 pods per noobaa component (core and db)
Keywords:
Status: NEW
Alias: None
Product: Red Hat OpenShift Container Storage
Classification: Red Hat
Component: Multi-Cloud Object Gateway
Version: 4.5
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: Nimrod Becker
QA Contact: Raz Tamir
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-20 08:22 UTC by Manjunatha
Modified: 2020-11-03 09:30 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
mmanjuna: needinfo?


Attachments (Terms of Use)

Description Manjunatha 2020-10-20 08:22:33 UTC
Description of problem (please be detailed as possible and provide log
snippests):
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).

Comment 4 Nimrod Becker 2020-10-20 08:49:33 UTC
4.6 is at dev freeze, as an RFE it should move to 4.7

Comment 5 Neha Berry 2020-10-20 19:04:05 UTC
@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

Comment 6 Nimrod Becker 2020-10-21 06:35:01 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.