CORTX-31239: Support variable timeout values in deploy-cortx-cloud.sh

[walterlopatka]

Description

There is a "wait" after each of the cortx helm charts are deployed. This wait is guarded by a timeout. Prior to this change the timeout values were hard-coded.

With this change in environment variable can override the timeout value. The supported environment variables are:

• CORTX_DEPLOY_CONTROL_TIMEOUT (default 300s)
• CORTX_DEPLOY_DATA_TIMEOUT (default 300s)
• CORTX_DEPLOY_SERVER_TIMEOUT (default 300s)
• CORTX_DEPLOY_HA_TIMEOUT (default 120s)

This value is passed directly to kubectl wait --timeout=${TIMEOUT}

This is being added so that CORTX developers can work around the previously hard-coded timeouts as needed.

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-31239

How was this tested?

Tested locally:

• Set short timeouts for CORTX_DEPLOY_CONTROL_TIMEOUT and CORTX_DEPLOY_HA_TIMEOUT and verified that they took effect
• Ran with standard timeouts to verify no change

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

[osowski]

lgtm