This page describes the upgrade policy for CockroachDB Cloud. For self-hosted clusters, see the CockroachDB Release Support Policy.
CockroachDB Cloud supports the latest major version of CockroachDB and the version immediately preceding it. Support for these versions includes patch version updates and security patches.
CockroachDB Serverless clusters are subject to automatic upgrades for both major and patch releases.
Patch version upgrades
Patch version releases, or "maintenance" releases, contain stable, backward-compatible improvements to the major versions of CockroachDB (for example, v21.2.0 → v21.2.1).
All CockroachDB Serverless and CockroachDB Dedicated clusters are subject to automatic upgrades to the latest supported patch version. To ensure that connections remain current during these upgrades, it's important to use connection retry logic in your application.
Single-node clusters will experience some downtime during cluster maintenance.
Major version upgrades
Major version releases (for example, v21.1.x → v21.2.x) contain new functionality and potentially backward-incompatible changes to CockroachDB.
Major version upgrades are automatic for CockroachDB Serverless clusters and opt-in for CockroachDB Dedicated clusters. Org Administrators must initiate major version upgrades for CockroachDB Dedicated clusters. When a new major version is available, Admins will be able to start an upgrade from the CockroachDB Cloud Console for clusters using the paid version of CockroachDB Dedicated. When a major version upgrade is initiated for a cluster, it will upgrade to the latest patch version as well.
Rollback support
When upgrading a CockroachDB Dedicated cluster to a new major version, once all nodes are running the new version, you have approximately 72 hours before the upgrade is automatically finalized. During this window, if you see unexpected behavior, you can trigger a rollback to the previous major version from the CockroachDB Cloud Console.
Note that you will roll back to the latest patch version of the previous major version, not the same patch version you were running before you initiated the upgrade.
If you see problems after the upgrade has been finalized, it will not be possible to roll back via the CockroachDB Cloud Console; you will have to reach out to support.
End of Support for older CockroachDB versions
As CockroachDB releases new major versions, older versions reach their End of Support (EOS) on CockroachDB Cloud. A CockroachDB version reaches EOS when it is two major versions behind the latest version. For example, when CockroachDB v21.2 was released, CockroachDB v20.2 reached EOS.
Clusters running unsupported CockroachDB versions are not eligible for our availability SLA. Further downgrades in support may occur as per the CockroachDB Release Support Policy.
If you are running a CockroachDB version nearing EOS, you will be reminded at least one month before that version’s EOS that your clusters must be upgraded by the EOS date to avoid losing support. A Org Administrator can upgrade your cluster directly from the CockroachDB Cloud Console.
See also
For more details about the upgrade and finalization process, see Upgrade to the Latest CockroachDB Version.
Was this helpful?
