Issue 241: Chart changes and CRD refactoring #245
Merged
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.
Signed-off-by: SrishT [email protected]
Change log description
Helm upgrade of the zookeeper operator and zookeeper cluster from 0.2.8 to 0.2.9-rc0 is failing. Also the
additionalPrinterColumns
from the ZookeeperCluster CRD have been removed.Purpose of the change
Fixes #241
What the code does
Changes the location of the CRD from the
crds/
since that was causing the operator upgrade from 0.2.8 to 0.2.9-rc0 to fail, and adds theadditionalPrinterColumns
back into the ZookeeperCluster CRD. Also adds default value for thestorageType
andkubernetesClusterDomain
fields so that helm upgrade of the zookeeper cluster using thereuse-values
flag does not fail.How to verify it