V0.11.0 branch

[walterlopatka]

Description

v0.11.0 Content

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
• [x] Merge code into main

CORTX image version requirements

This change requires the following images:

• cortx-data:2.0.0-902
• cortx-rgw:2.0.0-902
• cortx-control:2.0.0-902

How was this tested?

Standard cortx-k8s release testlist:

• automated deploy/destroy/start/shutdown/status
• S3 IO smoke test
• log-cortx-cloud.sh test
• upgrade test

Checklist

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

If this change requires newer CORTX or third party image versions:

• [ ] The image fields in solution.example.yaml have been updated to use the required versions.
• [ ] The appVersion field of the Helm chart has been updated to use the new CORTX version.

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 View rendered charts/cortx/README.md View rendered doc/advanced-deployment-scenarios.md

[keithpine]

This commit message was confusing though. https://github.com/Seagate/cortx-k8s/pull/357/commits/c4d9d860eca7dc25dce0bfbb73a7d75faa098221

[walterlopatka]

This commit message was confusing though. https://github.com/Seagate/cortx-k8s/commit/c4d9d860eca7dc25dce0bfbb73a7d75faa098221

Well... that is true.