From 04bfd22286905328d6ecd9646c88647d6303326f Mon Sep 17 00:00:00 2001
From: Ziming Zhang <zziming@vmware.com>
Date: Sun, 6 Mar 2022 19:21:41 +0800
Subject: [PATCH] use harbor v2.3.5 as default sample

Signed-off-by: Ziming Zhang <zziming@vmware.com>
---
 docs/LCM/upgrade-cluster.md                    | 6 +++---
 docs/tutorial.md                               | 2 +-
 manifests/samples/full_stack.yaml              | 2 +-
 manifests/samples/minimal_stack_fs.yaml        | 2 +-
 manifests/samples/minimal_stack_incluster.yaml | 2 +-
 manifests/samples/standard_stack.yaml          | 2 +-
 manifests/samples/standard_stack_fs.yaml       | 2 +-
 7 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/docs/LCM/upgrade-cluster.md b/docs/LCM/upgrade-cluster.md
index 8f2095745..a52fe01c8 100644
--- a/docs/LCM/upgrade-cluster.md
+++ b/docs/LCM/upgrade-cluster.md
@@ -6,9 +6,9 @@ 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
 
@@ -16,7 +16,7 @@ For upgrading Harbor cluster across different minor versions, an operator upgrad
 
 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
diff --git a/docs/tutorial.md b/docs/tutorial.md
index fd20d8999..c7e1088dd 100644
--- a/docs/tutorial.md
+++ b/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:
diff --git a/manifests/samples/full_stack.yaml b/manifests/samples/full_stack.yaml
index ca58562f0..2f75ddf45 100644
--- a/manifests/samples/full_stack.yaml
+++ b/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:
diff --git a/manifests/samples/minimal_stack_fs.yaml b/manifests/samples/minimal_stack_fs.yaml
index 6c9cb9b5f..a390961a6 100644
--- a/manifests/samples/minimal_stack_fs.yaml
+++ b/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
diff --git a/manifests/samples/minimal_stack_incluster.yaml b/manifests/samples/minimal_stack_incluster.yaml
index 38db08382..80299851d 100644
--- a/manifests/samples/minimal_stack_incluster.yaml
+++ b/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
diff --git a/manifests/samples/standard_stack.yaml b/manifests/samples/standard_stack.yaml
index 4ead24540..2d61e1a6e 100644
--- a/manifests/samples/standard_stack.yaml
+++ b/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:
diff --git a/manifests/samples/standard_stack_fs.yaml b/manifests/samples/standard_stack_fs.yaml
index c4cfa675b..4ae20c9a2 100644
--- a/manifests/samples/standard_stack_fs.yaml
+++ b/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