-
Notifications
You must be signed in to change notification settings - Fork 440
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Benedikt Bongartz <[email protected]>
- Loading branch information
Showing
2 changed files
with
59 additions
and
44 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| # Support | ||
|
|
||
| ## Go | ||
|
|
||
| When productised as a go libary or custom distribution the OpenTelemetry Operator project attempts to follow the supported go versions as [defined by the Go team](https://go.dev/doc/devel/release#policy). | ||
|
|
||
| Similar to the [opentelemetry collector](https://github.com/open-telemetry/opentelemetry-collector?tab=readme-ov-file#compatibility), removing support for an unsupported Go version is not considered a breaking change. | ||
|
|
||
| Support for Go versions on the OpenTelemetry Operator is updated as follows: | ||
|
|
||
| The first release after the release of a new Go minor version N will add build and tests steps for the new Go minor version. | ||
| The first release after the release of a new Go minor version N will remove support for Go version N-2. | ||
|
|
||
| Official OpenTelemetry Operator binaries may be built with any supported Go version. | ||
|
|
||
| # Compatibility matrix | ||
|
|
||
| ### OpenTelemetry Operator vs. OpenTelemetry Collector | ||
|
|
||
| The OpenTelemetry Operator follows the same versioning as the operand (OpenTelemetry Collector) up to the minor part of the version. For example, the OpenTelemetry Operator v0.18.1 tracks OpenTelemetry Collector 0.18.0. The patch part of the version indicates the patch level of the operator itself, not that of OpenTelemetry Collector. Whenever a new patch version is released for OpenTelemetry Collector, we'll release a new patch version of the operator. | ||
|
|
||
| By default, the OpenTelemetry Operator ensures consistent versioning between itself and the managed `OpenTelemetryCollector` resources. That is, if the OpenTelemetry Operator is based on version `0.40.0`, it will create resources with an underlying OpenTelemetry Collector at version `0.40.0`. | ||
|
|
||
| When a custom `Spec.Image` is used with an `OpenTelemetryCollector` resource, the OpenTelemetry Operator will not manage this versioning and upgrading. In this scenario, it is best practice that the OpenTelemetry Operator version should match the underlying core version. Given a `OpenTelemetryCollector` resource with a `Spec.Image` configured to a custom image based on underlying OpenTelemetry Collector at version `0.40.0`, it is recommended that the OpenTelemetry Operator is kept at version `0.40.0`. | ||
|
|
||
| ### OpenTelemetry Operator vs. Kubernetes vs. Cert Manager | ||
|
|
||
| We strive to be compatible with the widest range of Kubernetes versions as possible, but some changes to Kubernetes itself require us to break compatibility with older Kubernetes versions, be it because of code incompatibilities, or in the name of maintainability. Every released operator will support a specific range of Kubernetes versions, to be determined at the latest during the release. | ||
|
|
||
| We use `cert-manager` for some features of this operator and the third column shows the versions of the `cert-manager` that are known to work with this operator's versions. | ||
|
|
||
| The OpenTelemetry Operator _might_ work on versions outside of the given range, but when opening new issues, please make sure to test your scenario on a supported version. | ||
|
|
||
| | OpenTelemetry Operator | Kubernetes | Cert-Manager | | ||
| | ---------------------- | -------------- | ------------ | | ||
| | v0.97.0 | v1.23 to v1.29 | v1 | | ||
| | v0.90.0 | v1.23 to v1.28 | v1 | | ||
| | v0.96.0 | v1.23 to v1.29 | v1 | | ||
| | v0.95.0 | v1.23 to v1.29 | v1 | | ||
| | v0.94.0 | v1.23 to v1.29 | v1 | | ||
| | v0.93.0 | v1.23 to v1.29 | v1 | | ||
| | v0.92.0 | v1.23 to v1.29 | v1 | | ||
| | v0.91.0 | v1.23 to v1.29 | v1 | | ||
| | v0.89.0 | v1.23 to v1.28 | v1 | | ||
| | v0.88.0 | v1.23 to v1.28 | v1 | | ||
| | v0.87.0 | v1.23 to v1.28 | v1 | | ||
| | v0.86.0 | v1.23 to v1.28 | v1 | | ||
| | v0.85.0 | v1.19 to v1.28 | v1 | | ||
| | v0.84.0 | v1.19 to v1.28 | v1 | | ||
| | v0.83.0 | v1.19 to v1.27 | v1 | | ||
| | v0.82.0 | v1.19 to v1.27 | v1 | | ||
| | v0.81.0 | v1.19 to v1.27 | v1 | | ||
| | v0.80.0 | v1.19 to v1.27 | v1 | | ||
| | v0.79.0 | v1.19 to v1.27 | v1 | | ||
| | v0.78.0 | v1.19 to v1.27 | v1 | | ||
| | v0.77.0 | v1.19 to v1.26 | v1 | | ||
| | v0.76.1 | v1.19 to v1.26 | v1 | | ||
| | v0.75.0 | v1.19 to v1.26 | v1 | | ||
|
|