You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Removing tag v0.26.0 because it doesn't exist.
* Enabling users to choose the cert-manager version
* Adding Compatibility Matrix between Opentelemetry and Cert-manager
* Adding third column on Compatibility Matrix
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+5
Original file line number
Diff line number
Diff line change
@@ -46,6 +46,11 @@ In general, it's just easier to deploy the manager in a Kubernetes cluster inste
46
46
make cert-manager
47
47
```
48
48
49
+
In pursuit of continuous improvement, a variable named `CERTMANAGER_VERSION` which can be run:
50
+
```bash
51
+
CERTMANAGER_VERSION=1.60 make cert-manager
52
+
```
53
+
49
54
By default, it will generate an image following the format `quay.io/${USER}/opentelemetry-operator:${VERSION}`. You can set the following env vars in front of the `make` command to override parts or the entirety of the image:
50
55
51
56
*`IMG_PREFIX`, to override the registry, namespace and image name (`quay.io`)
Copy file name to clipboardexpand all lines: README.md
+17-16
Original file line number
Diff line number
Diff line change
@@ -195,31 +195,32 @@ The above CR can be queried by `kubectl get otelinst`.
195
195
196
196
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.
197
197
198
-
### OpenTelemetry Operator vs. Kubernetes
198
+
### OpenTelemetry Operator vs. Kubernetes vs. Cert Manager
199
199
200
200
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.
201
201
202
202
Our promise is that we'll follow what's common practice in the Kubernetes world and support N-2 versions, based on the release date of the OpenTelemetry Operator.
203
203
204
204
For instance, when we released v0.27.0, the latest Kubernetes version was v1.21.1. As such, the minimum version of Kubernetes we support for OpenTelemetry Operator v0.27.0 is v1.19 and we tested it with up to 1.21.
205
205
206
+
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.
207
+
206
208
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.
0 commit comments