CORTX-33598 - Updated max namespace length to 20 chars

[osowski]

Signed-off-by: Rick Osowski rosowski@gmail.com

Description

As part of previous changes for multiple Data and Server Pods per Worker Node, Pod FQDNs became longer and certain cases were causing cluster deployment to break post-deployment or fail completely. As such, a previous limit on namespace length was implemented to limit the exposure to these scenarios. Additional work has been done to support longer FQDNs throughout CORTX Core components, so this maximum namespace length limit can be increased.

Type of change

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

Applicable issues

• This change fixes an issue: #CORTX-33598
• This change is related to an issue: #

How was this tested?

Locally through many deploy/destroy loops with namespaces of length 8, 10, 15, 20, 25+ characters.

Additional information

Checklist

• [x] The change is tested and works locally.
• [x] 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:

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

---

View rendered README.md

[osowski]

At the moment, I believe it is the inclusion of the FQDN sub-domain as Labels in the Pod specs for the StatefulSets. We will need to do more investigation on if these are required into the future and/or if the prior HA functionality will be carried through as-is into CC. For now, we can increase this limitation to allow for more robust deployments and circle back to ensure we are driving the need to remove the limitation altogether.

A manual Chart deployment can definitely still fail, but the feedback is much more direct to the Helm user than the bash deploy script user and is more easily rectified.