Skip to content

chore: add RELEASE.md to document release process #2828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cdesiniotis wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: add RELEASE.md to document release process #2828

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
27 changes: 27 additions & 0 deletions RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# Release Process

The NVIDIA GPU Operator consists of the following artifacts:
- The NVIDIA GPU Operator container
- The NVIDIA GPU Operator helm chart
- The NVIDIA GPU Operator OLM bundle

The container and helm chart are published to nvcr.io.
The OLM bundle is published to the [Red Hat certified operators production catalog](https://github.com/redhat-openshift-ecosystem/certified-operators).
Comment on lines +8 to +9

@coderabbitai coderabbitai Bot Aug 28, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win

Correct the Helm chart publication destinations.

The supplied workflow publishes the chart to oci://ghcr.io/${repository_owner}/gpu-operator/charts, but this document lists nvcr.io and gh-pages. Update the artifact description and checklist to match the workflow. Keep nvcr.io or gh-pages only if separate publication steps exist and are documented.

Also applies to: 22-23


The NVIDIA GPU Operator is versioned following the calendar versioning convention.
To learn more about the project's versioning and lifecycle, refer to the [official documentation](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/platform-support.html#nvidia-gpu-operator-versioning).

# Release Process Checklist:
- [ ] Create a release PR:
- [ ] Create a new `bump-release-{{ .VERSION }}` branch
- [ ] Bump the project version in `versions.mk` and in the OLM bundle manifests in `bundle/manifests/`
- [ ] Create a PR from the created `bump-release-{{ .VERSION }}` branch
- [ ] Merge the release PR
- [ ] Tag the release and push the tag to the `internal` mirror
- [ ] Wait for the image to be published to nvcr.io
- [ ] Publish the helm chart to nvcr.io
- [ ] Publish the helm chart to the `gh-pages` branch
- [ ] Push the tag to the upstream GitHub repo
- [ ] Publish the OLM bundle to the certified operators catalog
- [ ] Create a PR in the [certified-operators](https://github.com/redhat-openshift-ecosystem/certified-operators) GitHub repository
- [ ] Publish the [release](https://github.com/NVIDIA/gpu-operator/releases)
Loading