chore: Change release process - Githubissues

kyma-project / opentelemetry-collector-components

Contains Otel Collector components that are not pushed to upstream (yet) or components that are Kyma specific

Apache License 2.0

2 stars 8 forks source link

chore: Change release process #67

Closed k15r closed 2 months ago

k15r commented 2 months ago

Description

Changes proposed in this pull request (what was done and why):

The release process of OCC should be tightly coupled to telemetry-manager. As the custom otel-col image is built to be used with telemetry manager we will only release a new version of the image alongside a new version of telemetry manager. This means: we will have a release branch indicating (by name) the telemetry-manager version it is released with. Within one telemetry-manager version the version of open telemetry collector is stable (e.g 0.104.X) For load-tests we will automatically bump the otel version using dependabot on main.

Released images will have the following tags:
- for load-tests: {OTEL-VERSION}-main
- for testing on PR level: PR-XXX
- for release with tm: {OTEL-VERSION}-{TM-VERSION}

Changes refer to particular issues, PRs or documents:

https://github.com/kyma-project/telemetry-manager/issues/1207

Traceability

[ ] The PR is linked to a GitHub issue.
[ ] The PR has a milestone set.
[ ] The PR has a respective area and kind label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[ ] If the change is user-facing, the documentation has been adjusted.
[ ] The feature is unit-tested.
[ ] The feature is e2e-tested.