This topic describes upgrade RisingWave in a K8s deployment with the RisingWave Kubernetes Operator and Helm.
When upgrading RisingWave, it’s important to be aware that there may be breaking changes. If you require technical support during the process of upgrading RisingWave in your production environments, please don’t hesitate to reach out to us.
Assuming that the Kubernetes namespace is default
, if your RisingWave cluster is deployed in another namespace, please add the -n <namespace>
argument to the kubectl
and helm
commands below. Remember to replace the <namespace>
with your own namespace.
The output should look like this:
To upgrade to the latest version:
To upgrade to a particular version:
Remember to replace all the <risingwave-cluster>
with the real object name.
Expected output:
<target-version>
with the target image version.Upgrading
condition becomes False
or empty.If wait timeouts, please check if the pods are running properly.
Expected output:
If any issue happens and it cannot be resolved within a certain timeframe, you can roll back the upgrade with the following command. Remember to replace the <version-before>
with the image version used before the upgrade. The other steps to verify the rollback are the same as the upgrade.
This topic describes upgrade RisingWave in a K8s deployment with the RisingWave Kubernetes Operator and Helm.
When upgrading RisingWave, it’s important to be aware that there may be breaking changes. If you require technical support during the process of upgrading RisingWave in your production environments, please don’t hesitate to reach out to us.
Assuming that the Kubernetes namespace is default
, if your RisingWave cluster is deployed in another namespace, please add the -n <namespace>
argument to the kubectl
and helm
commands below. Remember to replace the <namespace>
with your own namespace.
The output should look like this:
To upgrade to the latest version:
To upgrade to a particular version:
Remember to replace all the <risingwave-cluster>
with the real object name.
Expected output:
<target-version>
with the target image version.Upgrading
condition becomes False
or empty.If wait timeouts, please check if the pods are running properly.
Expected output:
If any issue happens and it cannot be resolved within a certain timeframe, you can roll back the upgrade with the following command. Remember to replace the <version-before>
with the image version used before the upgrade. The other steps to verify the rollback are the same as the upgrade.