Skip to content
This repository was archived by the owner on May 24, 2023. It is now read-only.

Commit cbb0414

Browse files
committed
Add OLM upgrade instructions (#141)
1 parent 4b4b9c8 commit cbb0414

File tree

1 file changed

+16
-0
lines changed

1 file changed

+16
-0
lines changed

docs/upgrades.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,22 @@
33
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
44
(see [the operator-sdk docs](https://sdk.operatorframework.io/docs/building-operators/golang/migration/) for more information).
55

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)
21+
622
## Manual upgrade - 0.2.0 to 0.3.0
723

824
### 1. Deploy the new operator

0 commit comments

Comments
 (0)