Closed suryakumar1024 closed 2 years ago
Thank you for your pull request and welcome to our community. We could not parse the GitHub identity of the following contributors: root. This is most likely caused by a git client misconfiguration; please make sure to:
git config --list | grep email
git config --global user.email email@example.com
@suryakumar1024 Please follow the instructions above from the cla-bot to ensure we can verify CLA signature, as well as following up on Codacy / Shellcheck issues identified in the PR.
I converted this to a draft, please mark "Ready for review" when it is no longer a WIP.
Signed-off-by: suryakumar.kumaravelan suryakumar.kumaravelan@seagate.com
Description
As per the proposed design, the master size limit should be split up accordingly and must be shared among components equally. Refer JIRA for detailed design: https://jts.seagate.com/browse/CORTX-33048
Current changes will get node/pod count and container count. With that, The size can be shared till container level.
TODO: Need to analysis and find the proper way to get number of components inside each container and further split the container level size limit among them.
Note: Support bundle also takes modules(components) filter parllely with size filter. This scenario need to be discussed and analsis.
Breaking change
Type of change
Applicable issues
CORTX image version requirements
This change requires the following images:
cortx-data:<version>
cortx-rgw:<version>
cortx-control:<version>
How was this tested?
Additional information
Checklist
If this change requires newer CORTX or third party image versions:
image
fields in solution.example.yaml have been updated to use the required versions.appVersion
field of the Helm chart has been updated to use the new CORTX version.If this change addresses a CORTX Jira issue:
CORTX-XXXXX:
)