Skip to content

Conversation

@jhlodin
Copy link
Contributor

@jhlodin jhlodin commented Oct 30, 2025

Disallowing Innovation releases on Basic/Standard and reframing support on Advanced as allowing access to bleeding-edge features.

https://cockroachlabs.atlassian.net/browse/DOC-15235

@netlify
Copy link

netlify bot commented Oct 30, 2025

Deploy Preview for cockroachdb-api-docs canceled.

Name Link
🔨 Latest commit cd6b6d8
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-api-docs/deploys/69126db644b8dd0008509888

@netlify
Copy link

netlify bot commented Oct 30, 2025

Deploy Preview for cockroachdb-interactivetutorials-docs canceled.

Name Link
🔨 Latest commit cd6b6d8
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-interactivetutorials-docs/deploys/69126db6f2d1660007856b1d

@github-actions
Copy link

Files changed:

@netlify
Copy link

netlify bot commented Oct 30, 2025

Netlify Preview

Name Link
🔨 Latest commit cd6b6d8
🔍 Latest deploy log https://app.netlify.com/projects/cockroachdb-docs/deploys/69126db69141fd0008404113
😎 Deploy Preview https://deploy-preview-20877--cockroachdb-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

@devarshishah3 devarshishah3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jhlodin Can you please add @celiala as a reviewer as well

@jhlodin jhlodin requested a review from celiala November 5, 2025 19:40
@jhlodin jhlodin force-pushed the jl/doc-15235 branch 2 times, most recently from 9d9ddcc to 1bacd7e Compare November 6, 2025 20:46
Copy link

@celiala celiala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes LGTM

For each release type, the end date of this period is called End of Support (EOS).

A cluster running an unsupported CockroachDB version is not eligible for Cockroach Labs’ [availability SLA](https://www.cockroachlabs.com/cloud-terms-and-conditions/cockroachcloud-technical-service-level-agreement/).
CockroachDB {{ site.data.products.basic }} and {{ site.data.products.standard }} clusters only support **Regular releases**. This ensures that these clusters are using versions of CockroachDB that receive a full year of support with routine patch updates. All CockroachDB {{ site.data.products.basic }} and {{ site.data.products.standard }} clusters are automatically upgraded to the next major Regular release upon its GA release.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a nuance here. All Basic clusters are automatically upgraded. If you have Standard cluster and have enabled manual upgrade, the cluster will not be automatically upgraded. The customer will have to take the action themselves. In this case, if the customer is running an EOS version (For standard, Regular release is EOS 12 months after the date of production release), they will be automatically upgraded to the next regular release.
If the customer has no manual upgrade set on Standard, they will be automatically upgraded

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The note underneath this paragraph spells out the nuance of setting Standard to handle manual upgrades/automatic upgrades happening after the EOS:

CockroachDB {{ site.data.products.standard }} clusters have the option to [disable automatic major-version upgrades]({% link cockroachcloud/cluster-management.md %}#manage-cluster-upgrades). In this case, you are responsible for upgrading the cluster before the current version hits the end-of-support (EOS) date in order to maintain uninterrupted support and SLA guarantees. Clusters that have not upgraded after the EOS date for that version are upgraded automatically.

I think it's more clear to give the default behavior, that Basic/Standard are upgraded automatically upon GA release, and allow the following paragraph to go into details about the scenario of setting Standard to upgrade manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants