Master OceanBase and OBproxy Upgrades on Kubernetes and Bare Metal

1. OceanBase Upgrade

1.1 Upgrade considerations

OceanBase cross‑version upgrades have specific requirements and limitations. Versions prior to V4.0.0.0 cannot be upgraded to V4.x, only certain paths such as V4.2.1 BP2 → V4.2.5 are supported, and some versions act as barriers requiring intermediate upgrades.

1.2 Business impact

The upgrade is transparent to applications; no write‑stop or service stop is needed. The cluster upgrades zones sequentially, and partition leaders switch between zones, so latency‑sensitive workloads should be upgraded during low‑traffic periods.

1.3 DBA operation notes

DDL is prohibited during certain phases and re‑enabled after upgrade.

major freeze is disabled for some version paths.

Migration, load balancing, physical backup/restore, switchover/failover, and new tenant creation are prohibited during upgrade.

1.4 OceanBase on Kubernetes upgrade

Command‑line method

Edit the oceanbase-test.yaml file and change spec.observer.image to the target version, then apply:

<code># before
spec:
  observer:
    image: oceanbase/oceanbase-cloud-native:4.2.0.0-101000032023091319
# after
spec:
  observer:
    image: oceanbase/oceanbase-cloud-native:4.2.1.1-101000062023110109
</code>

Apply the manifest and check pods:

<code>kubectl apply -f oceanbase-test.yaml -n oceanbase-test
kubectl get pods -n oceanbase-test
</code>

Dashboard method

Open the cluster overview page in OB‑Dash‑Board, click “Upgrade”, enter the new image address, and confirm.

1.5 OceanBase on bare metal (OCP) upgrade

Download the software package, upload it to OCP, select the target OB version in the OCP console, and submit the upgrade task.

2. OBproxy Upgrade

2.1 Upgrade considerations

Upgrade OBServer first, then OBproxy.

2.2 OBproxy on Kubernetes

Use OB‑Dash‑Board, select the OBproxy cluster, click “Edit” in the detailed configuration, and set the new image address.

2.3 OBproxy upgrade via OCP

Log into OCP, navigate to OBProxy, select the target cluster and open the overview page.

In the OBProxy list, click “Upgrade”, choose or upload the upgrade package, and confirm.

For batch upgrades, select multiple OBproxy instances, click “Batch Upgrade”, choose the package, and confirm.

3. OB‑Dash‑Board and OCP Platform Upgrade

3.1 OB‑Dash‑Board upgrade

Two methods: (1) reinstall via Helm – helm uninstall ob-ocp -n oceanbase-dashboard && helm install ob-ocp ob-operator/oceanbase-dashboard --version=0.3.1 -n oceanbase-dashboard ; (2) edit the Deployment and change the image.

3.2 OCP upgrade

Download the OCP all‑in‑one package, verify the latest obd version, install or upgrade the package, and run sh install.sh in the ocp-all-in-one/bin directory.

<code>obd --version
# install steps...
</code>

4. Summary

The article covers upgrade considerations and step‑by‑step procedures for OceanBase, OBproxy, OCP, and OB‑Dash‑Board in both Kubernetes and bare‑metal environments, enabling readers to perform complete upgrades confidently.