Open dingshun-cmss opened 1 week ago
aome additional info:
Can you show the logs for the kbcli upgrade kb?
Verify whether webhook is enabled:
kubectl get crd configconstraints.apps.kubeblocks.io -o jsonpath='{.spec.conversion}'
Verify whether webhook is enabled:
kubectl get crd configconstraints.apps.kubeblocks.io -o jsonpath='{.spec.conversion}'
Here's the output for this command on my test environment:
{"strategy":"None"}
Verify whether webhook is enabled:
kubectl get crd configconstraints.apps.kubeblocks.io -o jsonpath='{.spec.conversion}'
Here's the output for this command on my test environment:
{"strategy":"None"}
The conversion webhook is disable. Please show the kbcli/helm upgrade logs:
kbcli logs path:
$ ls -lrt ~/.kbcli/logs |tail -n 3
-rw-r--r-- 1 zhangtao staff 93550 7 Aug 14:52 kbcli-2024-08-07.log
-rw-r--r-- 1 zhangtao staff 10141 13 Aug 15:57 kbcli-2024-08-13.log
-rw-r--r-- 1 zhangtao staff 24684 3 Sep 18:21 kbcli-2024-09-03.log
@dingshun-cmss we will update the upgrade doc. Since KB 0.9.1 we will enable WebHook to support multi-version APIs.
Describe the Bug
After upgrading KubeBlocks in a test environment:
ConfigConstraint
objects are upgraded by the upgrade hook fromv1alpha1
tov1beta1
, but the converted content is incorrect.config-manager
container disappearing after the DB cluster Pod is regenerated.To Reproduce
ConfigConstraint
before the upgrade.ConfigConstraint
after the upgrade. I found that all the properties inspec
are missing, except forspec.immutableParameters
andspec.staticParameters
, which are retained.ConfigConstraint
s and restart the test cluster; theconfig-manager
container reappears.Expected Behavior
The
ConfigConstraint
conversion from the upgrade hook should generate the correct content.Additional Context
Upgrade from v0.8.4 to v0.9.1