@RunLLM, what is the recommended option to rollback after pulsar upgrade on a K8s deployment ?

The recommended option to rollback after a Pulsar upgrade on Kubernetes is to use Helm's rollback feature, which allows you to revert to a previous release. You can run

helm rollback <release-name> <revision>

to restore the cluster to a previous state. For more granular control, you can also use StatefulSet rollbacks with

kubectl rollout undo statefulset/<statefulset_name> --namespace <k8s_namespace>

if you need to revert specific components. Note that for BookKeeper/Bookie data compatibility, downgrades may fail if the storage format has changed between versions, especially with RocksDB or BookKeeper upgrades, so always check compatibility before rolling back (source, source, source). Would you like more detail on handling data compatibility or specific rollback scenarios? Sources: - Bug: Downgrade issue (Pulsar GitHub) - https://pulsar.apache.org/docs/3.2.x/helm-upgrade - https://docs.streamnative.io/private/restart-cluster-1.11.0 👍 0 button 👎 0 button 💡 Hint: Mention @runllm in the thread for followups.