Change the resource requirement base calculation from 6 to 3 OSDs #2385
Conversation
In 4.16 when we implemented this change we had assumed the base to be 6 OSDs, but since than we have added a lot more pods to the ODF deployment. The ODF docs also mention the resource requirement to be based on 3 OSDs Signed-off-by: Malay Kumar Parida <[email protected]>
malayparida2000
force-pushed
the
osd_count
branch
from
11fa7e9 to
94778dc
Compare
|
/cherry-pick release-4.20 |
|
@malayparida2000: once the present PR merges, I will cherry-pick it on top of In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cc @SanjalKatiyar |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bipuladh, malayparida2000 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-merge-bot
bot
merged commit e8b3d37
into
red-hat-storage:master
|
@malayparida2000: new pull request created: #2393 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: new pull request created: #2394 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.18 |
|
@malayparida2000: #2385 failed to apply on top of branch "release-4.15": In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.18 |
|
@malayparida2000: new pull request created: #2395 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.17 |
|
/cherry-pick release-4.16 |
|
@malayparida2000: new pull request created: #2396 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: new pull request created: #2397 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/cherry-pick release-4.20-compatibility |
|
@malayparida2000: new pull request created: #2413 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: new pull request created: #2414 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: new pull request created: #2415 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: new pull request created: #2416 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
@malayparida2000: cannot checkout In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
3 participants
In 4.16 when we implemented this change we had assumed the base to be 6 OSDs, but since than we have added a lot more pods to the ODF deployment.
The ODF docs also mention the resource requirement to be based on 3 OSDs
Ref-https://issues.redhat.com/browse/DFBUGS-4484