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
Copy file name to clipboardExpand all lines: docs/DEVELOPMENT.md
+18-3Lines changed: 18 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -80,7 +80,7 @@ make catalog-build
80
80
make catalog-push
81
81
```
82
82
83
-
## Installing the Operator using OpenShift Web console
83
+
## Installing the Operator using OpenShift Web console
84
84
85
85
### Create Custom Operator Catalog
86
86
@@ -115,10 +115,10 @@ The new operator should be now available for installation from the OpenShift web
115
115
## Installing the Operator using CLI
116
116
117
117
When deploying the Operator using CLI, cert-manager needs to be installed otherwise
118
-
webhook will not start. `cert-manager` is not required when deploying via the web console as OLM
118
+
webhook will not start. `cert-manager` is not required when deploying via the web console as OLM
119
119
takes care of webhook certificate management. You can read more on this [here](https://olm.operatorframework.io/docs/advanced-tasks/adding-admission-and-conversion-webhooks/#deploying-an-operator-with-webhooks-using-olm)
@@ -131,5 +131,20 @@ Uncomment all entries marked with `[CERTMANAGER]` in manifest files under `confi
131
131
make install && make deploy
132
132
```
133
133
134
+
### Updating versions
134
135
136
+
When starting a new version, the locations tagged with `OSC_VERSION` should be updated with the new version number. A few places are also tagged with `OSC_VERSION_BEFORE`, referring to the version being replaced.
135
137
138
+
On the `main` branch `1.5.2`, the following locations were identified, but looking for the version pattern would give too many false positives on `devel` with `1.7.0`, and even more false positives were found with `1.8.0`. Most hits were in `go.mod` or `go.sum` and should be ignored, since they refer to dependencies with unrelated version numbering.
0 commit comments