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
@@ -77,7 +78,7 @@ See [upgrade docs](./docs/upgrades.md)
77
78
78
79
We publish NGINX Ingress Operator releases on GitHub. See our [releases page](https://github.com/nginxinc/nginx-ingress-helm-operator/releases).
79
80
80
-
The latest stable release is [3.0.1](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v3.0.1). For production use, we recommend that you choose the latest stable release.
81
+
The latest stable release is [3.1.0](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v3.1.0). For production use, we recommend that you choose the latest stable release.
2. To deploy the Operator and associated resources to all environments, run:
15
15
16
16
```shell
17
-
make deploy IMG=nginx/nginx-ingress-operator:3.0.1
17
+
make deploy IMG=nginx/nginx-ingress-operator:3.1.0
18
18
```
19
19
20
20
2. Check that the Operator is running:
@@ -30,11 +30,11 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace.
30
30
31
31
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):
Copy file name to clipboardExpand all lines: docs/openshift-installation.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -23,10 +23,10 @@ Additional steps:
23
23
24
24
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):
0 commit comments