Deploy with custom Chart values

Description

Specify a custom values.yaml file when using the deployment script to add or override calculated values. This makes it possible to configure things not supported by solution.yaml, for example, enabling the Consul Web UI by default.

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
[ ] Documentation additions or improvements
[ ] Code quality improvements to existing code or test additions/updates

How was this tested?

❯ cat myvalues.yaml 
consul:
  ui:
    enabled: true

Deploy with the above values file, and I can see the Consul UI is enabled.

Specify a non-existent file, and see an error is report and the deploy script exits before installing.

Specify a blank env var, or none at all, and notice a normal, unmodified deployment (no Consul UI).

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:

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

View rendered README.md

Seagate / cortx-k8s