chore: apply suggestions from CR

GreptimeTeam · Sep 9, 2024 · 9459ef8 · 9459ef8
1 parent 7697563
commit 9459ef8
Show file tree

Hide file tree

Showing 2 changed files with 26 additions and 18 deletions.
diff --git a/...s/deploy-on-kubernetes/manage-greptimedb-operator/deploy-greptimedb-operator.md b/...s/deploy-on-kubernetes/manage-greptimedb-operator/deploy-greptimedb-operator.md
@@ -29,28 +29,36 @@ greptime/greptimedb-operator	0.2.3        	0.1.0-alpha.29	The greptimedb-operato
 ```
 
 ### Install the Operator
-To install the Operator, run the following `helm install` command. This command also creates a dedicated namespace `greptimedb-operator` for the installation. It's recommended to use a dedicated namespace for the Operator:
+To install the Operator, run the following `helm install` command. This command also creates a dedicated namespace `greptimedb-admin` for the installation. It's recommended to use a dedicated namespace for the Operator:
 ```bash
 helm install \
   operator greptime/greptimedb-operator \
   --create-namespace \
-  -n greptimedb-operator
+  -n greptimedb-admin
 ```
 
-### Verify the Operator installation
-After installation, check the contents of the `greptimedb-operator` namespace to confirm that all pods and services are running correctly:
+### Verify the CRD installation
+Check the contents of the `greptimedb-admin` namespace to confirm that all Custom Resource Definitions (CRDs) have been installed correctly:
+
 ```bash
-kubectl get all -n greptimedb-operator
+kubectl get crds -n greptimedb-admin
 ```
 
 You should see output similar to this:
 ```bash
-NAME                                       READY   STATUS    RESTARTS   AGE
-pod/operator-8495fcb545-jpz2m              1/1     Running   0          17s
+NAME                                CREATED AT
+greptimedbclusters.greptime.io      2024-09-09T07:54:07Z
+greptimedbstandalones.greptime.io   2024-09-09T07:54:07Z
+```
 
-NAME                                  READY   UP-TO-DATE   AVAILABLE   AGE
-deployment.apps/operator              1/1     1            1           17s
+### Verify the Operator installation
+After installation, check the contents of the `greptimedb-admin` namespace to confirm that all pods are running correctly:
+```bash
+kubectl get pods -n greptimedb-admin
+```
 
-NAME                                             DESIRED   CURRENT   READY   AGE
-replicaset.apps/operator-8495fcb545              1         1         1       17s
+You should see output similar to this:
+```bash
+NAME                                            READY   STATUS    RESTARTS   AGE
+operator-greptimedb-operator-7d58cb8f7c-jz46g   1/1     Running   0          26s
 ```
diff --git a/.../deploy-on-kubernetes/manage-greptimedb-operator/upgrade-greptimedb-operator.md b/.../deploy-on-kubernetes/manage-greptimedb-operator/upgrade-greptimedb-operator.md
@@ -3,24 +3,24 @@ You can upgrade the GreptimeDB Operator at any time without impacting your manag
 
 ### Verify the existing Operator installation.
 
-First, verify the health and status of all Operator pods and services using:
+First, verify the health and status of all Operator pods using:
 
 ```bash
-kubectl get all -n greptimedb-operator
+kubectl get pods -n greptimedb-admin
 ```
 
-If the Operator was installed in a custom namespace, replace `greptimedb-operator` with your specific namespace using `-n <NAMESPACE>`.
+If the Operator was installed in a custom namespace, replace `greptimedb-admin` with your specific namespace using `-n <NAMESPACE>`.
 
 Next, view the installed Helm charts in the namespace:
 
 ```bash
-helm list -n greptimedb-operator
+helm list -n greptimedb-admin
 ```
 
 You should see output similar to this:
 ```
 NAME               	NAMESPACE          	REVISION	UPDATED                                	STATUS  	CHART                    	APP VERSION
-operator	        greptimedb-operator	1       	2024-08-30 08:04:53.388756424 +0000 UTC	deployed	greptimedb-operator-0.2.1	0.1.0-alpha.28
+operator	        greptimedb-admin    1       	2024-08-30 08:04:53.388756424 +0000 UTC	deployed	greptimedb-operator-0.2.1	0.1.0-alpha.28
 ```
 
 The Operator is currently installed with version `0.1.0-alpha.28` using the `greptimedb-operator-0.2.1` chart.
@@ -55,7 +55,7 @@ greptime/greptimedb-operator	0.2.3        	0.1.0-alpha.29	The greptimedb-operato
 
 Use Helm to upgrade the GreptimeDB Operator to the latest version:
 ```bash
-helm upgrade -n greptimedb-operator \
+helm upgrade -n greptimedb-admin \
   operator greptime/greptimedb-operator
 ```
 
@@ -67,7 +67,7 @@ The command should return a successful upgrade with an incremented `REVISION` va
 
 To confirm the upgrade, run the following command:
 ```bash
-kubectl get pod -l 'app.kubernetes.io/name=operator' -n greptimedb-operator -o json | jq '.items[0].spec.containers[0].image'
+kubectl get pod -l 'app.kubernetes.io/name=operator' -n greptimedb-admin -o json | jq '.items[0].spec.containers[0].image'
 ```
 
 You should see the following output, indicating that the Operator has been successfully upgraded to the latest version: