diff --git a/CHANGELOG.md b/CHANGELOG.md index bc763590..e026bc45 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,9 @@ # Changelog +### 1.4.1 + +An automatically generated list of changes can be found on Github at: [1.4.1 Release](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v1.4.1) + ### 1.4.0 An automatically generated list of changes can be found on Github at: [1.4.0 Release](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v1.4.0) diff --git a/Makefile b/Makefile index 5e3e21a7..22b5dfaa 100644 --- a/Makefile +++ b/Makefile @@ -3,7 +3,7 @@ # To re-generate a bundle for another specific version without changing the standard setup, you can: # - use the VERSION as arg of the bundle target (e.g make bundle VERSION=0.0.2) # - use environment variables to overwrite this value (e.g export VERSION=0.0.2) -VERSION ?= 1.4.0 +VERSION ?= 1.4.1 # CHANNELS define the bundle channels used in the bundle. # Add a new line here if you would like to change its default config. (E.g CHANNELS = "candidate,fast,stable") diff --git a/README.md b/README.md index d7430424..3af1ba5b 100644 --- a/README.md +++ b/README.md @@ -14,7 +14,7 @@ The following table shows the relation between the versions of the two projects: | NGINX Ingress Controller | NGINX Ingress Operator | |--------------------------|------------------------| -| 3.1.x | 1.4.0 | +| 3.1.x | 1.4.1 | | 3.0.x | 1.3.1 | | 2.4.x | 1.2.1 | | 2.3.x | 1.1.0 | @@ -64,7 +64,7 @@ See [upgrade docs](./docs/upgrades.md) ## NGINX Ingress Operator Releases We publish NGINX Ingress Operator releases on GitHub. See our [releases page](https://github.com/nginxinc/nginx-ingress-helm-operator/releases). -The latest stable release is [1.4.0](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v1.4.0). For production use, we recommend that you choose the latest stable release. +The latest stable release is [1.4.1](https://github.com/nginxinc/nginx-ingress-helm-operator/releases/tag/v1.4.1). For production use, we recommend that you choose the latest stable release. ## Development diff --git a/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml b/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml index a025eb02..d7d32b6d 100644 --- a/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml +++ b/bundle/manifests/nginx-ingress-operator.clusterserviceversion.yaml @@ -176,8 +176,8 @@ metadata: capabilities: Basic Install categories: Monitoring, Networking certified: "true" - containerImage: nginx/nginx-ingress-operator:1.4.0 - createdAt: "2023-05-17T00:04:34Z" + containerImage: nginx/nginx-ingress-operator:1.4.1 + createdAt: "2023-05-17T18:30:11Z" description: The NGINX Ingress Operator is a Kubernetes/OpenShift component which deploys and manages one or more NGINX/NGINX Plus Ingress Controllers operatorframework.io/suggested-namespace: nginx-ingress @@ -190,7 +190,7 @@ metadata: operatorframework.io/arch.arm64: supported operatorframework.io/arch.ppc64le: supported operatorframework.io/arch.s390x: supported - name: nginx-ingress-operator.v1.4.0 + name: nginx-ingress-operator.v1.4.1 namespace: placeholder spec: apiservicedefinitions: {} @@ -394,7 +394,7 @@ spec: - --metrics-bind-address=127.0.0.1:8080 - --leader-elect - --leader-election-id=nginx-ingress-operator - image: nginx/nginx-ingress-operator:1.4.0 + image: nginx/nginx-ingress-operator:1.4.1 livenessProbe: httpGet: path: /healthz @@ -485,4 +485,4 @@ spec: minKubeVersion: 1.21.0 provider: name: NGINX Inc - version: 1.4.0 + version: 1.4.1 diff --git a/config/manager/kustomization.yaml b/config/manager/kustomization.yaml index 3aba3a1d..5dfd4d9f 100644 --- a/config/manager/kustomization.yaml +++ b/config/manager/kustomization.yaml @@ -5,4 +5,4 @@ kind: Kustomization images: - name: controller newName: nginx/nginx-ingress-operator - newTag: 1.4.0 + newTag: 1.4.1 diff --git a/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml b/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml index 6e9a8eec..09499119 100644 --- a/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml +++ b/config/manifests/bases/nginx-ingress-operator.clusterserviceversion.yaml @@ -176,7 +176,7 @@ metadata: capabilities: Basic Install categories: Monitoring, Networking certified: "true" - containerImage: nginx/nginx-ingress-operator:1.4.0 + containerImage: nginx/nginx-ingress-operator:1.4.1 createdAt: placeholder description: The NGINX Ingress Operator is a Kubernetes/OpenShift component which deploys and manages one or more NGINX/NGINX Plus Ingress Controllers @@ -345,7 +345,7 @@ spec: - --metrics-bind-address=127.0.0.1:8080 - --leader-elect - --leader-election-id=nginx-ingress-operator - image: nginx/nginx-ingress-operator:1.4.0 + image: nginx/nginx-ingress-operator:1.4.1 livenessProbe: httpGet: path: /healthz @@ -451,4 +451,4 @@ spec: minKubeVersion: 1.21.0 provider: name: NGINX Inc - version: 1.4.0 + version: 1.4.1 diff --git a/docs/manual-installation.md b/docs/manual-installation.md index a3a7ee7a..0cf5d9e8 100644 --- a/docs/manual-installation.md +++ b/docs/manual-installation.md @@ -8,17 +8,17 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace. ``` git clone https://github.com/nginxinc/nginx-ingress-helm-operator/ cd nginx-ingress-helm-operator/ - git checkout v1.4.0 + git checkout v1.4.1 ``` 2. `OpenShift` To deploy the Operator and associated resources to an OpenShift environment, run: ``` - make deploy IMG=nginx/nginx-ingress-operator:1.4.0 + make deploy IMG=nginx/nginx-ingress-operator:1.4.1 ``` 3. Alternatively, to deploy the Operator and associated resources to all other environments: ``` - make deploy IMG=nginx/nginx-ingress-operator:1.4.0 + make deploy IMG=nginx/nginx-ingress-operator:1.4.1 ``` 2. Check that the Operator is running: @@ -33,4 +33,4 @@ This will deploy the operator in the `nginx-ingress-operator-system` namespace. 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, 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/v1.4.0/resources/scc.yaml` +`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v1.4.1/resources/scc.yaml` diff --git a/docs/openshift-installation.md b/docs/openshift-installation.md index 9b66c853..cb4c409a 100644 --- a/docs/openshift-installation.md +++ b/docs/openshift-installation.md @@ -21,6 +21,6 @@ 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, 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/v1.4.0/resources/scc.yaml` +`kubectl apply -f https://raw.githubusercontent.com/nginxinc/nginx-ingress-helm-operator/v1.4.1/resources/scc.yaml` You can now deploy the NGINX Ingress Controller instances.