upgrades.md

Upgrade - 0.2.0 to 0.3.0

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 (see the operator-sdk docs for more information).

OLM upgrade - 0.2.0 to 0.3.0

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.

1. Uninstall the existing 0.2.0 operator

Uninstall the operator using the web console - see the OCP documentation for details.

2. Reinstall the latest version of the operator

Install the latest version of the Operator following the steps outlined in OpenShift installation doc.

3. Upgrade the existing ingress controller deployments

Upgrade to the latest 1.12.0 Ingress Controller image - see the release notes here

Manual upgrade - 0.2.0 to 0.3.0

1. Deploy the new operator

Deploy the operator following the steps outlined in manual installation doc.

2. Cleanup the existing operator

Uninstall the existing operator deployment:

1. Checkout the previous version of the nginx-ingress-operator 0.3.0.
2. Uninstall the resources by running the following commands (be sure to edit files to suit your environment, if required):

   kubectl delete -f deploy/operator.yaml
   kubectl delete -f deploy/role_binding.yaml
   kubectl delete -f deploy/role.yaml
   kubectl delete -f deploy/service_account.yaml
   

3. Upgrade the existing ingress controller deployments

Upgrade to the latest 1.12.0 Ingress Controller image - see the release notes here