release: v21.1.0-rc.1

[tbg]

Candidate SHA: 413f48e2156165698189eeeb6f5ea32254322422
Deployment status: Request Qualification Clusters
Make and Publish Build: https://teamcity.cockroachdb.com/buildConfiguration/Internal_Release_MakeAndPublishBuild/2940299 v21.1.0-beta.5-51-g413f48e215
Qualify Build: https://teamcity.cockroachdb.com/buildConfiguration/Internal_Release_Qualify/2940363
Publish Cockroach Release: WIP EDIT ME WIP.

CC Clusters Running the Build:

• requested SREOPS-1864

Admin UI for Qualification Clusters:

• Old Version: WIP EDIT ME WIP.
• New Version: WIP EDIT ME WIP.

Working Tags:

• Build ID: v21.1.0-beta.5-51-g413f48e215
• staging-* tag: elided - if we need another cherry-pick that means chosing a new release-21.1 sha

Release process checklist

Prep date: WIP fill in date to roll out: usually Monday, a week before the release WIP

• 2. Pick a SHA

• fill in Candidate SHA above

• fill in staging-* Tag above (alpha/beta only)

• fill in Build ID above

• fill in Make and Publish Build above

• fill in Qualify Build above

• 3. Announce the release to releases@

• 4. Ask SRE to run the build on some CC clusters

5-8: Qualify the Release. See Release Qualification

• Short-running Checks:
• 5. Verify node crash reports
• Qualification Clusters:
• 6. Setup Qualification Clusters
• Check sentry panic propagation
• fill in all WIP elements above (Admin UI, etc.)

Monitoring the Qualification Clusters (ideally one day after creation, halfway through the week, and before the release):

• 7. Keep an eye on clusters until release date.

Do not proceed below until the release date.

Release date: WIP fill in date: usually Monday WIP

• 7 continued: Check cluster status
• 8. Destroy clusters
• 9. Publish Cockroach Release
• Acked security@ and release-engineering-team@ on the generated AWS S3 bucket write alert to confirm these writes were part of a planned release (See Publish Cockroach Release for details).
• 10. Check binaries
• 11. Check docker image
• 12. Remove staging branch / tags from repository
• 13.Announce the release is cut to releases@
• 14. Update version numbers
• For production or stable releases in the latest major release series only (in August 2020, this is the v20.1 series):
• Update Brew Recipe
• Update Orchestrator configurations:CRDB
• Update Orchestrator configurations:Helm Charts
• For all production or stable releases:
• Create a ticket in the Dev Inf tracker to update the Red Hat Container Image Repository as outlined in https://github.com/cockroachlabs/cockroach-redhat-deploy/blob/main/README.md.
• After docs are updated Announce version to registration cluster
• Update version map in bin/roachtest and regenerate test fixtures
• 15. Update docs (handled by Docs team)
• 16. External communications for release (handled by Marketing eam)

Cleanup:

• Remove staging branch / tags from repository
• Destroy roachprod clusters

[tbg]

Another change that we need to pick up was just merged (#64370 ), so the above SHA is invalid. We'll start again.

[tbg]

Upon realizing that #64370 is only fixing half of a problem spanning back several releases, and the fix for the other half is still in the works (#64471) we decided to forward with rc.1 as is after all.