update version 1.1.2

Signed-off-by: Ziming Zhang <zziming@vmware.com>

charts/harbor-operator/README.md

@@ -37,7 +37,7 @@ Deploy Harbor Operator
 | harborClass | string | `""` | Class name of the Harbor operator |
 | image.pullPolicy | string | `"IfNotPresent"` | The image pull policy for the controller. |
 | image.repository | string | `"goharbor/harbor-operator"` | The image repository whose default is the chart appVersion. |
-| image.tag | string | `"v1.1.1"` | The image tag whose default is the chart appVersion. |
+| image.tag | string | `"v1.1.2"` | The image tag whose default is the chart appVersion. |
 | imagePullSecrets | list | `[]` | Reference to one or more secrets to be used when pulling images <https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/> For example: `[   {"name":"image-pull-secret"} ]` |
 | installCRDs | bool | `false` | If true, CRD resources will be installed as part of the Helm chart. If enabled, when uninstalling CRD resources will be deleted causing all installed custom resources to be DELETED |
 | leaderElection.namespace | string | `"kube-system"` | The namespace used to store the ConfigMap for leader election |

charts/harbor-operator/values.yaml

@@ -4,7 +4,7 @@ image:
   # image.pullPolicy -- The image pull policy for the controller.
   pullPolicy: IfNotPresent
   # image.tag -- The image tag whose default is the chart appVersion.
-  tag: v1.1.1
+  tag: v1.1.2
 
 # installCRDs -- If true, CRD resources will be installed as part of the Helm chart. If enabled, when uninstalling CRD resources will be deleted causing all installed custom resources to be DELETED
 installCRDs: false

docs/installation/by-helm-chart.md

@@ -36,13 +36,13 @@ There are several ways to get the Harbor operator helm chart:
     git clone https://github.com/goharbor/harbor-operator.git && \
     cd harbor-operator && \
     git checkout release-1.1.0 && \
-    make helm-generate RELEASE_VERSION=v1.1.1
+    make helm-generate RELEASE_VERSION=v1.1.2
 
     # Checkout to the specified branch or the specified tag
     # To branch: git checkout <branch-name> e.g.: git checkout release-1.1.0
-    # To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.1 -b tag-v1.1.1
+    # To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.2 -b tag-v1.1.2
 
-    # chart is generated to `charts/harbor-operator-v1.1.1.tgz`
+    # chart is generated to `charts/harbor-operator-v1.1.2.tgz`
     ```
 
 ## Deploy Harbor operator with chart
@@ -53,7 +53,7 @@ Run the `helm` command to install the harbor operator to your cluster:
 
 ```shell
 # Change chart path depends on how do you get the helm chart.
-helm upgrade --namespace harbor-operator-ns --install harbor-operator charts/harbor-operator-v1.1.1.tgz --set-string image.repository=ghcr.io/goharbor/harbor-operator --set-string image.tag=v1.1.1
+helm upgrade --namespace harbor-operator-ns --install harbor-operator charts/harbor-operator-v1.1.2.tgz --set-string image.repository=ghcr.io/goharbor/harbor-operator --set-string image.tag=v1.1.2
 ```
 
 For what settings you can override with `--set`, `--set-string`, `--set-file` or `--values`, you can refer to the [values.yaml](../../charts/harbor-operator/values.yaml) file.

docs/installation/enable_minio_console.md

@@ -18,8 +18,8 @@ First, clone the code from the `harbor-operator` repository.
 git clone https://github.com/goharbor/harbor-operator.git
 
 # Checkout to the specified branch or the specified tag.
-# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.1
-# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.1 -b tag-v1.1.1
+# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.2
+# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.2 -b tag-v1.1.2
 ```
 
 Then open the [all-in-one](./kustomization-all-in-one.md) kustomization manifest and locate the `patchesStrategicMerge` section. Comment the patch `- patch/delete-minio-console.yaml`.

docs/installation/kustomization-all-in-one.md

@@ -47,8 +47,8 @@ If you want to customize the deployment manifest like editing image settings of
 git clone https://github.com/goharbor/harbor-operator.git
 
 # Checkout to the specified branch or the specified tag.
-# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.1
-# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.1 -b tag-v1.1.1
+# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.2
+# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.2 -b tag-v1.1.2
 ```
 
 As the resource manifests are not stored in the codebase, then you need to run the following command to generate the related resource manifests before using `kustomize` to build your customized operator deployment manifest:

docs/installation/kustomization-custom.md

@@ -133,8 +133,8 @@ Of course, you can clone the codebase into your computer and then customize and
 git clone https://github.com/goharbor/harbor-operator.git
 
 # Checkout to the specified branch or the specified tag.
-# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.1
-# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.1 -b tag-v1.1.1
+# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.2
+# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.2 -b tag-v1.1.2
 
 # As the resource manifests are not stored in the codebase, then you need to run the following command to generate the related resource manifests before using `kustomize` to build your customized operator deployment manifest:
 make manifests

docs/makefile.md

@@ -10,8 +10,8 @@ Clone the harbor operator codebase into your computer with command
 git clone https://github.com/goharbor/harbor-operator.git
 
 # Checkout to the specified branch or the specified tag.
-# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.1
-# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.1 -b tag-v1.1.1
+# To branch: git checkout <branch-name> e.g.: git checkout release-1.1.2
+# To tag: git checkout tags/<tag> -b <branch-name> e.g: git checkout tags/v1.1.2 -b tag-v1.1.2
 ```
 
 The `Makefile` is in the root dir of the code repository.