Skip to content

Commit 37ca451

Browse files
committed
Add updating the Helm Chart to the release guide
1 parent df75f9c commit 37ca451

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

RELEASE.md

+2-1
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,8 @@ Steps to release a new version of the OpenTelemetry Operator:
1515
1. Add the changes to the changelog by running `make chlog-update VERSION=$VERSION`.
1616
1. Check the OpenTelemetry Collector's changelog and ensure migration steps are present in `pkg/collector/upgrade`
1717
1. Once the changes above are merged and available in `main`, one of the maintainers will tag the release.
18-
1. The GitHub Workflow will take it from here, creating a GitHub release with the generated artifacts (manifests) and publishing the images
18+
1. The GitHub Workflow will take it from here, creating a GitHub release with the generated artifacts (manifests) and publishing the images.
19+
1. Update the operator version in the Helm Chart, as per the [release guide](https://github.com/open-telemetry/opentelemetry-helm-charts/blob/main/charts/opentelemetry-operator/CONTRIBUTING.md)
1920
1. The GitHub Workflow, submits two pull requests to the Operator hub repositories. Make sure the pull requests are approved and merged.
2021
1. `community-operators-prod` is used by OLM on OpenShift. Example: [`operator-framework/community-operators-prod`](https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/494)
2122
1. `community-operators` is used by Operatorhub.io. Example: [`operator-framework/community-operators`](https://github.com/k8s-operatorhub/community-operators/pull/461)

0 commit comments

Comments
 (0)