Merge pull request #2030 from molliezhang/master

deploy-clickhouse zh&en : Update the expected output
This commit is contained in:
KubeSphere CI Bot 2021-11-03 14:14:07 +08:00 committed by GitHub
commit 78c678f7c6
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 19 additions and 16 deletions

View File

@ -23,7 +23,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
1. Log in to the KubeSphere Web console as `admin`, and use **Kubectl** from the **Toolbox** in the bottom-right corner to run the following command to install ClickHouse Operator. It is recommended that you have at least two worker nodes available in your cluster.
```bash
kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/master/clickhouse-operator-install.yml
$ kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/master/clickhouse-operator-install.yml
```
{{< notice note >}}
@ -34,11 +34,13 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
2. You can see the expected output as below if the installation is successful.
```
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallations.clickhouse.qingcloud.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallationtemplates.clickhouse.qingcloud.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseoperatorconfigurations.clickhouse.qingcloud.com created
```powershell
$ kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/main/clickhouse-operator-install.yml
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallations.clickhouse.radondb.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallationtemplates.clickhouse.radondb.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseoperatorconfigurations.clickhouse.radondb.com created
serviceaccount/clickhouse-operator created
clusterrole.rbac.authorization.k8s.io/clickhouse-operator-kube-system created
clusterrolebinding.rbac.authorization.k8s.io/clickhouse-operator-kube-system created
configmap/etc-clickhouse-operator-files created
configmap/etc-clickhouse-operator-confd-files created
@ -52,7 +54,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
3. You can run the following command to view the status of ClickHouse Operator resources.
```bash
kubectl get all --selector=app=clickhouse-operator -n kube-system
$ kubectl get all --selector=app=clickhouse-operator -n kube-system
```
Expected output:
@ -116,7 +118,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
2. In the window that appears, run the following command and then navigate to the username and password of the ClickHouse cluster.
```bash
kubectl edit chi clickho-749j8s -n demo-project
$ kubectl edit chi clickho-749j8s -n demo-project
```
![get-username-password](/images/docs/appstore/external-apps/deploy-clickhouse/get-username-password.png)
@ -130,7 +132,7 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
3. Run the following command to access the ClickHouse cluster, and then you can use command like `show databases` to interact with it.
```bash
kubectl exec -it chi-clickho-749j8s-all-nodes-0-0-0 -n demo-project -- clickhouse-client --user=clickhouse --password=c1ickh0use0perator
$ kubectl exec -it chi-clickho-749j8s-all-nodes-0-0-0 -n demo-project -- clickhouse-client --user=clickhouse --password=c1ickh0use0perator
```
![use-clickhouse](/images/docs/appstore/external-apps/deploy-clickhouse/use-clickhouse.png)
@ -140,4 +142,3 @@ This tutorial demonstrates how to deploy ClickHouse Operator and a ClickHouse Cl
In the above command, `chi-clickho-749j8s-all-nodes-0-0-0` is the Pod name and you can find it in **Pods** under **Application Workloads**. Make sure you use your own Pod name, project name, username, and password.
{{</ notice >}}

View File

@ -23,7 +23,7 @@ weight: 14340
1. 以 `admin` 身份登录 KubeSphere 的 Web 控制台,并使用**工具箱**中的 **Kubectl** 执行以下命令来安装 ClickHouse Operator。建议至少准备 2 个可用集群节点。
```bash
kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/main/clickhouse-operator-install.yml
$ kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/main/clickhouse-operator-install.yml
```
{{< notice note >}}
@ -35,10 +35,12 @@ weight: 14340
**预期结果**
```powershell
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallations.clickhouse.altinity.com configured
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallationtemplates.clickhouse.altinity.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseoperatorconfigurations.clickhouse.altinity.com created
$ kubectl apply -f https://raw.githubusercontent.com/radondb/radondb-clickhouse-kubernetes/main/clickhouse-operator-install.yml
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallations.clickhouse.radondb.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseinstallationtemplates.clickhouse.radondb.com created
customresourcedefinition.apiextensions.k8s.io/clickhouseoperatorconfigurations.clickhouse.radondb.com created
serviceaccount/clickhouse-operator created
clusterrole.rbac.authorization.k8s.io/clickhouse-operator-kube-system created
clusterrolebinding.rbac.authorization.k8s.io/clickhouse-operator-kube-system created
configmap/etc-clickhouse-operator-files created
configmap/etc-clickhouse-operator-confd-files created
@ -52,7 +54,7 @@ weight: 14340
2. 执行如下命令可查看 ClickHouse Operator 资源状态。
```bash
kubectl get all --selector=app=clickhouse-operator -n kube-system
$ kubectl get all --selector=app=clickhouse-operator -n kube-system
```
**预期结果**
```
@ -149,7 +151,7 @@ weight: 14340
2. 打开终端窗口,执行如下命令,并输入 ClickHouse 集群用户名和密码。
```bash
kubectl edit chi <app name> -n <project name>
$ kubectl edit chi <app name> -n <project name>
```
{{< notice note >}}
@ -163,7 +165,7 @@ weight: 14340
3. 执行如下命令,访问 ClickHouse 集群,并可通过 `show databases` 命令查看数据库。
```bash
kubectl exec -it <pod name> -n <project name> -- clickhouse-client --user=<user name> --password=<user password>
$ kubectl exec -it <pod name> -n <project name> -- clickhouse-client --user=<user name> --password=<user password>
```
{{< notice note >}}