use harbor v2.3.5 as default sample

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

docs/LCM/upgrade-cluster.md

@@ -6,17 +6,17 @@ A specified version of Harbor operator supports a corresponding Harbor minor ver
 
 The guideline shown below describes how to upgrade your Harbor cluster from lower patch version to higher patch version without operator upgrading (because there is no need as a Harbor operator version supports all patch releases).
 
-Assume that the harbor operator v1.0.1 which serves harbor v2.2.x is installed in the Kubernetes cluster, and there is a harbor cluster v2.2.2 deployed in the Kubernetes cluster.
+Assume that the harbor operator v1.1.1 which serves harbor v2.3.x is installed in the Kubernetes cluster, and there is a harbor cluster v2.3.2 deployed in the Kubernetes cluster.
 
-If you want to upgrade the harbor cluster from v2.2.2 to v2.2.3, just edit the manifest of the harbor cluster by `kubectl` and set the `version` field from `2.2.2` to `2.2.3` and the harbor operator will upgrade the harbor cluster instance to harbor v2.2.3.
+If you want to upgrade the harbor cluster from v2.3.2 to v2.3.5, just edit the manifest of the harbor cluster by `kubectl` and set the `version` field from `2.3.2` to `2.3.5` and the harbor operator will upgrade the harbor cluster instance to harbor v2.3.5.
 
 ## Upgrade to minor+ releases
 
 For upgrading Harbor cluster across different minor versions, an operator upgrading should be involved first (because one Harbor operator version only serves one minor version serials). Steps shown below describes how to do such upgrading.
 
 1. Upgrade the harbor operator to the newer version that supports the Harbor version you're planning to upgrade your existing Harbor cluster to by `helm` or `kustomize`, the method depends on the original way to install the harbor operator. [Installation](../installation/installation.md) is a reference resources to upgrade the harbor operator to new release.
 
-1. Edit the manifest of the harbor cluster by `kubectl` and set the `version` field to the newer Harbor version (e.g:`2.3.3`) in the spec.
+1. Edit the manifest of the harbor cluster by `kubectl` and set the `version` field to the newer Harbor version (e.g:`2.3.5`) in the spec.
 
    ```bash
    kubectl -n harbor-cluster-ns edit harborclusters cluster-name

docs/tutorial.md

@@ -121,7 +121,7 @@ metadata:
   name: harborcluster-sample
   namespace: cluster-sample-ns
 spec:
-  version: 2.3.3
+  version: 2.3.5
   logLevel: info
   network:
     ipFamilies:

manifests/samples/full_stack.yaml

@@ -67,7 +67,7 @@ metadata:
   name: harborcluster-sample
   namespace: cluster-sample-ns
 spec:
-  version: 2.3.3
+  version: 2.3.5
   logLevel: info
   network:
     ipFamilies:

manifests/samples/minimal_stack_fs.yaml

@@ -68,7 +68,7 @@ metadata:
   name: harborcluster-sample
   namespace: cluster-sample-ns
 spec:
-  version: 2.3.3
+  version: 2.3.5
   logLevel: info
   imageSource:
     repository: ghcr.io/goharbor

manifests/samples/minimal_stack_incluster.yaml

@@ -67,7 +67,7 @@ metadata:
   name: harborcluster-sample
   namespace: cluster-sample-ns
 spec:
-  version: 2.3.3
+  version: 2.3.5
   logLevel: info
   imageSource:
     repository: ghcr.io/goharbor

manifests/samples/standard_stack.yaml

@@ -201,7 +201,7 @@ spec:
         host: harbor-redis-master
         passwordRef: harbor-redis
         port: 6379
-  version: 2.3.3
+  version: 2.3.5
   chartmuseum: {}
   core:
     tokenIssuer:

manifests/samples/standard_stack_fs.yaml

@@ -119,7 +119,7 @@ metadata:
   name: harborcluster-sample
   namespace: cluster-sample-ns
 spec:
-  version: 2.3.3
+  version: 2.3.5
   logLevel: info
   imageSource:
     repository: ghcr.io/goharbor