CORTX-31350: Expose Cpu & Memory limits for all CORTX Services

[osowski]

Description

This PR adds support for CORTX Pod's requests and limits for CPU & Memory when deploying to Kubernetes. This configuration capability is exposed through the solution.yaml interface and interned by the deploy scripts and Helm Charts to apply the specific values to the deployed Pods and generated ConfigMaps. Users can now control the amount of CPU & Memory deployed CORTX artifacts will have available directly from solution.yaml.

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds new functionality)
• Breaking change (bug fix or new feature that breaks existing functionality)
• Third-party dependency update
• Documentation additions or improvements
• Code quality improvements to existing code or test additions/updates

Applicable issues

• This change fixes an issue: CORTX-31350
• This change is related to an issue: Feature F-40B (CORTX-27851)

How was this tested?

Tested locally with using default requests & limits, as well as customizing requests & limits per Kubernetes standards.

Checklist

• The change is tested and works locally.
• New or changed settings in the solution YAML are documented clearly in the README.md file.
• All commits are signed off and are in agreement with the CORTX Community DCO and CLA policy.

If this change addresses a CORTX Jira issue:

• The title of the PR starts with the issue ID (e.g. CORTX-XXXXX:)

---

View rendered README.md

[walterlopatka]

lgtm

[keithpine]

solution-check.yaml is missing the newly added required resource values.

[keithpine]

I didn't test personally, but LGTM.