Upgrade - 0.5.1 to 1.0.0

Release 1.0.0 includes a backward incompatible change from version 0.5.1 as we have moved from a Go based operator to a Helm based operator.

OLM upgrade - 0.5.1 to 1.0.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. In OpenShift, this can be done by setting the Approval Strategy to Manual. Please see the Operator SDK docs for more details on the Operator Capability Levels.

Upgrade CRDs
Uninstall Go operator -> this will also remove any instances of the NginxIngressController, but not any dependent objects (ingresses, VSs, etc)
Remove the nginx-ingress ingressClass k delete ingressclass/nginx
Install new operator
Deploy common resources (scc, default server secret, ns, etc). Note: Multiple NIC deployments: the RBAC resources should be deployed separately if deploying multiple ICs in same namespace. This is because only one of the ICs in a namespace will be assigned "ownership" of these resources. Similarly, the IngressClass resource needs to be created separately if deploying mutiple NIC instances with a shared IngressClass. See the README for more information
Re-create ingress controllers (note: multi IC rules) using the new Operator. Be sure to use the same configuration as the previous deployments (ingress class name, namespaces etc). They will pick up all deployed dependant resources.

0. Upgrade the existing NIC crds

Navigate here and run kubectl apply -f crds/

1. Uninstall the existing 0.5.1 operator, the nginx ingress controller CRD, and the ingressClass

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

Next uninstall the NIC CRD nginxingresscontrollers.k8s.nginx.org. This will remove any instances of the NginxIngressController, but not any dependent objects (ingresses, VSs, etc).

Finally, remove the nginx-ingress ingressClass k delete ingressclass/nginx.

2. Install the latest version of the operator

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

3. Deploy new ingress controller deployments

Use the new Nginx Ingress Operator installation to deploy Nginx Ingress Controller - see the release notes here and a guide to the Helm configuration parameters here

Manual upgrade - 0.5.1 to 1.0.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:

Checkout the previous version of the nginx-ingress-operator 0.5.1.
Uninstall the resources by running the following command:
```
make undeploy
```

3. Install the latest version of the operator

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

3. Deploy new ingress controller deployments

Use the new Nginx Ingress Operator installation to deploy Nginx Ingress Controller - see the release notes here and a guide to the Helm configuration parameters here

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!