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
{{ message }}
This repository was archived by the owner on May 24, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: docs/upgrades.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,6 +3,22 @@
3
3
Release 0.3.0 includes a major upgrade of the Operator-SDK which has resulted in a number of changes in the layout of the project
4
4
(see [the operator-sdk docs](https://sdk.operatorframework.io/docs/building-operators/golang/migration/) for more information).
5
5
6
+
## OLM upgrade - 0.2.0 to 0.3.0
7
+
8
+
**Note: The `nginx-ingress-operator` supports basic install only - we do not support auto-updates. When you are installing the Operator using the OLM, the auto-update feature should be disabled to avoid breaking changes being auto-applied.**
9
+
10
+
### 1. Uninstall the existing 0.2.0 operator
11
+
12
+
Uninstall the operator using the web console - see [the OCP documentation for details](https://access.redhat.com/documentation/en-us/openshift_container_platform/4.6/pdf/operators/OpenShift_Container_Platform-4.6-Operators-en-US.pdf).
13
+
14
+
### 2. Reinstall the latest version of the operator
15
+
16
+
Install the latest version of the Operator following the steps outlined in [OpenShift installation doc](./openshift-installation.md).
17
+
18
+
### 3. Upgrade the existing ingress controller deployments
19
+
20
+
Upgrade to the latest 1.12.0 Ingress Controller image - see the release notes [here](https://docs.nginx.com/nginx-ingress-controller/releases/#nginx-ingress-controller-1-12-0)
0 commit comments