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
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,14 @@ Learn more about operators in the [Kubernetes Documentation](https://kubernetes.
8
8
9
9
To install a specific version of the NGINX Ingress Controller with the operator, a specific version of the NGINX Ingress Operator is required.
10
10
11
-
Up until version 0.5.0, this Operator was Go based. Version 1.0.0 marks an uncompatible upgrade as this release swtiched the Operator to being Helm-based, built from the [NGINX Ingress Controller Helm chart](http://helm.nginx.com/#nginx-ingress-controller). The configuration for the Helm chart can be seen in the [NGINX Ingress Controller documentation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/#configuration).
11
+
Up until version 0.5.1, this Operator was Go based. Version 1.0.0 marks an uncompatible upgrade as this release swtiched the Operator to being Helm-based, built from the [NGINX Ingress Controller Helm chart](http://helm.nginx.com/#nginx-ingress-controller). The configuration for the Helm chart can be seen in the [NGINX Ingress Controller documentation](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/#configuration).
12
12
13
13
The following table shows the relation between the versions of the two projects:
`controller.volumeMounts`| The volumeMounts of the Ingress Controller pods. | []
140
143
`controller.initContainers`| InitContainers for the Ingress Controller pods. | []
141
144
`controller.extraContainers`| Extra (eg. sidecar) containers for the Ingress Controller pods. | []
142
-
`controller.resources`| The resources of the Ingress Controller pods. | {}
145
+
`controller.resources` | The resources of the Ingress Controller pods. | requests: cpu=100m,memory=128Mi
143
146
`controller.replicaCount`| The number of replicas of the Ingress Controller deployment. | 1
144
147
`controller.ingressClass`| A class of the Ingress Controller. An IngressClass resource with the name equal to the class must be deployed. Otherwise, the Ingress Controller will fail to start. The Ingress Controller only processes resources that belong to its class - i.e. have the "ingressClassName" field resource equal to the class. The Ingress Controller processes all the VirtualServer/VirtualServerRoute/TransportServer resources that do not have the "ingressClassName" field for all versions of kubernetes. | nginx
145
148
`controller.setAsDefaultIngress`| New Ingresses without an `"ingressClassName"` field specified will be assigned the class specified in `controller.ingressClass`. | false
Copy file name to clipboardExpand all lines: docs/upgrades.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# Upgrade - 0.5.0 to 1.0.0
1
+
# Upgrade - 0.5.1 to 1.0.0
2
2
3
-
Release 1.0.0 includes a backward incompatible change from version 0.5.0 as we have moved from a Go based operator to a Helm based operator.
3
+
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.
4
4
5
-
## OLM upgrade - 0.5.0 to 1.0.0
5
+
## OLM upgrade - 0.5.1 to 1.0.0
6
6
7
7
**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](https://sdk.operatorframework.io/docs/advanced-topics/operator-capabilities/operator-capabilities/) for more details on the Operator Capability Levels.**
8
8
1. Upgrade CRDs
@@ -17,7 +17,7 @@ Release 1.0.0 includes a backward incompatible change from version 0.5.0 as we h
17
17
18
18
Navigate [here](../helm-charts/nginx-ingress/) and run ` kubectl apply -f crds/`
19
19
20
-
### 1. Uninstall the existing 0.5.0 operator, the nginx ingress controller CRD, and the ingressClass
20
+
### 1. Uninstall the existing 0.5.1 operator, the nginx ingress controller CRD, and the ingressClass
21
21
22
22
Uninstall the operator using the web console - see [the OCP documentation for details](https://access.redhat.com/documentation/en-us/openshift_container_platform/4.9/pdf/operators/OpenShift_Container_Platform-4.9-Operators-en-US.pdf).
23
23
@@ -33,7 +33,7 @@ Install the latest version of the Operator following the steps outlined in [Open
33
33
34
34
Use the new Nginx Ingress Operator installation to deploy Nginx Ingress Controller - see the release notes [here](https://docs.nginx.com/nginx-ingress-controller/releases/#nginx-ingress-controller-2-2-0) and a guide to the Helm configuration parameters [here](https://docs.nginx.com/nginx-ingress-controller/installation/installation-with-helm/#configuration)
35
35
36
-
## Manual upgrade - 0.5.0 to 1.0.0
36
+
## Manual upgrade - 0.5.1 to 1.0.0
37
37
38
38
### 1. Deploy the new operator
39
39
@@ -43,7 +43,7 @@ Deploy the operator following the steps outlined in [manual installation doc](./
43
43
44
44
Uninstall the existing operator deployment:
45
45
46
-
1. Checkout the previous version of the nginx-ingress-operator [0.5.0](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v0.5.0).
46
+
1. Checkout the previous version of the nginx-ingress-operator [0.5.1](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v0.5.0).
47
47
2. Uninstall the resources by running the following command:
`controller.volumeMounts` | The volumeMounts of the Ingress Controller pods. | []
177
177
`controller.initContainers` | InitContainers for the Ingress Controller pods. | []
178
178
`controller.extraContainers` | Extra (eg. sidecar) containers for the Ingress Controller pods. | []
179
-
`controller.resources` | The resources of the Ingress Controller pods. | {}
179
+
`controller.resources` | The resources of the Ingress Controller pods. | requests: cpu=100m,memory=128Mi
180
180
`controller.replicaCount` | The number of replicas of the Ingress Controller deployment. | 1
181
181
`controller.ingressClass` | A class of the Ingress Controller. An IngressClass resource with the name equal to the class must be deployed. Otherwise, the Ingress Controller will fail to start. The Ingress Controller only processes resources that belong to its class - i.e. have the "ingressClassName" field resource equal to the class. The Ingress Controller processes all the VirtualServer/VirtualServerRoute/TransportServer resources that do not have the "ingressClassName" field for all versions of kubernetes. | nginx
182
182
`controller.setAsDefaultIngress` | New Ingresses without an `"ingressClassName"` field specified will be assigned the class specified in `controller.ingressClass`. | false
0 commit comments