You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For an existing KubeBlocks Add-On, we added a sidecar container to one of the components in the ClusterDefinition. After upgrading the add-on using Helm, the KubeBlocks Pod started crashing continuously.
Steps to Reproduce
To reproduce the behavior in a KubeBlocks 0.8.4 environment:
Install the initial version of the KubeBlocks add-on.
Create a cluster using this add-on.
Modify the KubeBlocks add-on by adding a sidecar container with specific configurations and startup scripts.
Use helm upgrade to upgrade the modified KubeBlocks add-on.
Check the status of the KubeBlocks operator Pods. The operator Pod will crash continuously.
Expected Behavior
The KubeBlocks operator should continue to operate normally after the upgrade.
Screenshots
Here is a screenshot of the crash:
Additional Context
KubeBlocks Version: 0.8.4
The text was updated successfully, but these errors were encountered:
shanshanying
changed the title
[BUG] KubeBlocks 0.8.4 Crashes After Adding a Container to an Existing Add-On
[BUG] KubeBlocks 0.8.4 Crashes After Updating SVC to Existing Clusters.
Jan 20, 2025
Describe the Bug
For an existing KubeBlocks Add-On, we added a sidecar container to one of the components in the
ClusterDefinition
. After upgrading the add-on using Helm, the KubeBlocks Pod started crashing continuously.Steps to Reproduce
To reproduce the behavior in a KubeBlocks 0.8.4 environment:
helm upgrade
to upgrade the modified KubeBlocks add-on.Expected Behavior
The KubeBlocks operator should continue to operate normally after the upgrade.
Screenshots
Here is a screenshot of the crash:
Additional Context
The text was updated successfully, but these errors were encountered: