This repository has been archived by the owner on Feb 8, 2024. It is now read-only.
CORTX-30140: Zookeeper managed as cortx Helm Chart dependency #236
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add Zookeeper as a dependency to the new CORTX chart. In this case, Zookeeper is already a dependency of Kafka, so we let the Kafka chart manage it. Follow up to PRs #230 and #233.
Breaking change
Type of change
Applicable issues
CORTX image version requirements
How was this tested?
Deployed a new release using this PR. Performed basic I/O.
Tested backwards compatibility by deploying a release prior to this PR. Then ran all of the updated utility scripts against that deployment (although, see Additional information).
Additional information
The status-cortx-cloud.sh script will report a failure for Zookeeper Cluster IP services when running against an earlier deployment, since the names of the services have changed. I don't consider this a breaking change, since the status script should reflect what is expected based on how it is supposed to be deployed with the current version.
Checklist
If this change addresses a CORTX Jira issue:
CORTX-XXXXX:
)View rendered charts/cortx/README.md