Skip to content

Latest commit

 

History

History
32 lines (19 loc) · 2.25 KB

openshift-installation.md

File metadata and controls

32 lines (19 loc) · 2.25 KB

Installation in an OpenShift cluster using the OLM

This installation method is the recommended way for OpenShift users. Note: OpenShift version must be 4.2 or higher.

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.

The NGINX Ingress Operator is a RedHat certified Operator.

  1. In the OpenShift dashboard, click Operators > Operator Hub in the left menu and use the search box to type nginx ingress: alt text
  2. Click the NGINX Ingress Operator and click Install: alt text
  3. Click Subscribe: alt text

OpenShift will install the NGINX Ingress Operator:

alt text

Note: If you're upgrading your operator installation to a later release, navigate here and run kubectl apply -f crds/ or oc apply -f crds/ as a prerequisite

Additional steps:

In order to deploy NGINX Ingress Controller instances into OpenShift environments, a new SCC is required to be created on the cluster which will be used to bind the specific required capabilities to the NGINX Ingress service account(s). To do so for NIC deployments, please run the following command (assuming you are logged in with administrator access to the cluster):

kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.0.0/resources/scc.yaml

Alternatively, to create an SCC for NIC daemonsets, please run this command:

kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v3.0.0/resources/scc-daemonset.yaml

You can now deploy the NGINX Ingress Controller instances.