-
Notifications
You must be signed in to change notification settings - Fork 446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After upgrading to 0.17, an exception error occurs when modifying clickhouseinstallation #842
Comments
How exactly do you upgrade to 0.17? Could you share the results for following command?
|
Could you upgrade CRDs first Could you remove this deployment (it safe) kubecetl delete deploy -n kube-system clickhouse-operator-altinity-clickhouse-operator after it and just apply kubectl apply -f https://raw.githubusercontent.com/Altinity/clickhouse-operator/master/deploy/operator/clickhouse-operator-install-bundle.yaml and check results kubectl get deploy clickhouse-operator -n kube-system |
I wrote the helm chart deployment myself |
@czhfe ok. try update crds |
Now I do not understand why the operator and crd updated here will error, there is no solution |
It solution cause new CRDs define status as subresources. Compare your current CRDs with |
I upgraded from 0.13.5 to 0.17 |
Do you have Could you share the following command results? kubectl get chi -n ch1 clickhouse -o yaml |
Yes, I have tested this before by deleting the |
Problem recurrence: The /spec/templating/policy in the clickhouseinstallations.clickhouse.altinity.com CRD prior to version 0.16.0 did not have its default value explicitly defined, resulting in that default value being "". |
Should be fixed in earlier released, but additional rules were added at https://github.com/Altinity/clickhouse-operator/releases/tag/release-0.22.1 |
After upgrading to 0.17 an exception error occurs when modifying clickhouseinstallation, which prevents modification and deletion of clickhouseinstallation. the error is as follows:
The ClickHouseInstallation "clickhouse" is invalid: status.errors: Invalid value: "null": status.errors in body must be of type array: "null"
The text was updated successfully, but these errors were encountered: