本文首发于 Nebula Graph Community 公众号
嗨，大家好！Nebula Operator 开源也有一段时间了，之前也有一篇相干的博客介绍，然而实际相干的博客却还没有，当初：
它来了！来了！它带着实际走来了！
Nebula Operator 介绍
对于 Nebula Operator 的介绍，大家能够参考之前那篇博客：一文详解云上自动化部署集群管理工具 Nebula Operator。
本文将次要侧重于实际方向，让你能很快地动手 Nebula Operator，体验图数据库的乐趣！
Nebula Operator云上实际
到这里，开始进入正题，本文将应用阿里云进行 Nebula Operator 实际，其余云厂商相似。
装置工具
本次实际须要在操作电脑上装置如下根底工具：
- Kubectl
- Helm
- Docker
以上根底工具相干的装置办法请参考对应链接。
创立云上 Kubernetes
因为 Operator 是依靠于 Kubernetes 的，所以在进行 Nebula Operator 实际之前，须要先筹备好 Kubernetes 环境。
首先进入到阿里云的控制台，而后进入到容器服务 Kubernetes 版，再创立一个集群。此实际抉择的是 ACK 托管版，相干的创立参数请按需抉择。
留神： 为了不便外网拜访 Kubernetes API Server ，本次实际勾选了应用 EIP 裸露 API Server，你能够依据本身状况抉择是否启用，如果不开启，你须要买通操作电脑与 Kubernetes 的之间网络。其余参数请按需抉择。
期待 Kubernetes 集群启动后，将集群的连贯信息中公网拜访中的内容复制到计算机$HOME/.kube/config文件中。
而后你能够应用如下命令验证下 Kubernetes 集群：
$ kubectl get nodesNAME STATUS ROLES AGE VERSIONcn-beijing.192.168.250.13 Ready <none> 51m v1.20.4-aliyun.1cn-beijing.192.168.250.185 Ready <none> 51m v1.20.4-aliyun.1cn-beijing.192.168.250.89 Ready <none> 51m v1.20.4-aliyun.1装置 Nebula Operator 依赖
在装置 Nebula Operator 之前，还须要先装置一些依赖。
装置 CertManager
# 装置 CertManager$ helm install cert-manager cert-manager --repo https://charts.jetstack.io \ --namespace cert-manager --create-namespace --version v1.3.1 \ --set installCRDs=true# 稍等一会儿，检测 CertManager 是否启动失常$ kubectl -n cert-manager get podNAME READY STATUS RESTARTS AGEcert-manager-7998c69865-jfw9x 1/1 Running 0 93scert-manager-cainjector-7b744d56fb-846w9 1/1 Running 0 93scert-manager-webhook-7d6d4c78bc-ssk4w 1/1 Running 0 93s装置 OpenKruise
# 装置 OpenKruise$ helm install kruise \ https://github.com/openkruise/kruise/releases/download/v0.8.1/kruise-chart.tgz# 稍等一会儿，检测 OpenKruise 是否启动失常$ kubectl -n kruise-system get podNAME READY STATUS RESTARTS AGEkruise-controller-manager-6797f89d9b-ppv65 1/1 Running 0 49skruise-controller-manager-6797f89d9b-wlkbd 1/1 Running 0 49skruise-daemon-7rljq 1/1 Running 0 49skruise-daemon-8kd8d 1/1 Running 0 49skruise-daemon-n6tdw 1/1 Running 0 49s增加 Nebula Operator Charts
# 增加 Nebula Operator Charts Repo$ helm repo add nebula-operator https://vesoft-inc.github.io/nebula-operator/charts# 更新 repo$ helm repo update装置 Nebula Operator
因为阿里云上无奈拉取gcr.io和k8s.gcr.io镜像，因而须要指定国内镜像，这里进行了如下替换：
| 原镜像 | 替换后镜像 |
|---|---|
| gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 | kubesphere/kube-rbac-proxy:v0.8.0 |
| k8s.gcr.io/kube-scheduler:v1.18.8 | kubesphere/kube-scheduler:v1.18.8 |
你能够通过如下命令查看所有能够设置的参数：
$ helm show values nebula-operator/nebula-operator此次实际中的装置命令如下：
# 装置 Nebula Operator$ helm install nebula-operator nebula-operator/nebula-operator \ --namespace nebula-operator-system --create-namespace --version 0.1.0 \ --set image.kubeRBACProxy.image=kubesphere/kube-rbac-proxy:v0.8.0 \ --set image.kubeScheduler.image=kubesphere/kube-scheduler:v1.18.8# 稍等一会儿，检测 Nebula Operator 是否启动失常$ kubectl -n nebula-operator-system get podNAME READY STATUS RESTARTS AGEnebula-operator-controller-manager-deployment-6968547fff-k62b4 2/2 Running 0 19snebula-operator-controller-manager-deployment-6968547fff-lhpdx 2/2 Running 0 19snebula-operator-scheduler-deployment-7c5fc7945-hbkv8 2/2 Running 0 19snebula-operator-scheduler-deployment-7c5fc7945-sxc7w 2/2 Running 0 19s如果你自定义了 Kubernetes 的 Cluster Domain ，则须要批改装置命令，减少设置kubernetesClusterDomain，如下：
# 装置 Nebula Operator ，请批改 <<YourCustomCLusterDomain>>$ helm install nebula-operator nebula-operator/nebula-operator \ --namespace nebula-operator-system --create-namespace --version 0.1.0 \ --set image.kubeRBACProxy.image=kubesphere/kube-rbac-proxy:v0.8.0 \ --set image.kubeScheduler.image=kubesphere/kube-scheduler:v1.18.8 \ --set kubernetesClusterDomain=<<YourCustomCLusterDomain>>部署 Nebula Cluster
至此，Nebula Operator 曾经就绪，接下来装置Nebula Cluster来体验图数据吧！
首先，须要获取StorageClass，这个将会用来设置Nebula Cluster所应用的存储。
$ kubectl get scNAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGEalicloud-disk-available diskplugin.csi.alibabacloud.com Delete Immediate true 100malicloud-disk-efficiency diskplugin.csi.alibabacloud.com Delete Immediate true 100malicloud-disk-essd diskplugin.csi.alibabacloud.com Delete Immediate true 100malicloud-disk-ssd diskplugin.csi.alibabacloud.com Delete Immediate true 100malicloud-disk-topology diskplugin.csi.alibabacloud.com Delete WaitForFirstConsumer true 100m从下面得悉，阿里云目前反对5种StorageClass。此次实际将会应用alicloud-disk-ssd。其余云厂商会有对应的StorageClass，请依照理论状况进行抉择。
*留神：每个云厂商可能对于申请存储的大小有范畴限度，比方阿里云对于 SSD 限度在20 Gi到32,768 Gi，在创立Nebula Cluster的时候须要留神下。
你能够通过如下命令查看所有能够设置的参数：
$ helm show values nebula-operator/nebula-cluster此次实际中的装置命令如下：
# 创立 Nebula Cluster 的名称$ export NEBULA_CLUSTER_NAME=nebula# 创立 Nebula Cluster 的 namespace$ export NEBULA_CLUSTER_NAMESPACE=nebula# 创立 Nebula Cluster 的 StorageClass 名称，这里设置为之前查找到的 alicloud-disk-ssd$ export STORAGE_CLASS_NAME=alicloud-disk-ssd# 创立 Nebula Cluster 中每个组建所应用存储的大小$ export STORAGE_SIZE_GRAPHD=20Gi$ export STORAGE_SIZE_METAD=20Gi$ export STORAGE_SIZE_STORAGED=20Gi# 创立 Nebula Cluster$ helm install ${NEBULA_CLUSTER_NAME} nebula-operator/nebula-cluster \ --namespace ${NEBULA_CLUSTER_NAMESPACE} --create-namespace --version 0.1.0 \ --set nameOverride=${NEBULA_CLUSTER_NAME} \ --set nebula.storageClassName="${STORAGE_CLASS_NAME}" \ --set nebula.graphd.storage="${STORAGE_SIZE_GRAPHD}" \ --set nebula.metad.storage="${STORAGE_SIZE_METAD}" \ --set nebula.storaged.storage="${STORAGE_SIZE_STORAGED}"# 稍等一会儿，检测 Nebula Cluster 是否启动失常$ kubectl -n ${NEBULA_CLUSTER_NAMESPACE} get nebulaclusterNAME GRAPHD-DESIRED GRAPHD-READY METAD-DESIRED METAD-READY STORAGED-DESIRED STORAGED-READY AGEnebula 2 2 3 3 3 3 4m10s$ kubectl -n ${NEBULA_CLUSTER_NAMESPACE} get podNAME READY STATUS RESTARTS AGEnebula-graphd-0 1/1 Running 0 96snebula-graphd-1 1/1 Running 0 96snebula-metad-0 1/1 Running 0 97snebula-metad-1 1/1 Running 0 97snebula-metad-2 1/1 Running 0 97snebula-storaged-0 1/1 Running 0 97snebula-storaged-1 1/1 Running 0 97snebula-storaged-2 1/1 Running 0 97s当然，也能够将Storaged实例降级到5个，执行命令如下：
# 降级 Nebula Cluster$ helm upgrade ${NEBULA_CLUSTER_NAME} nebula-operator/nebula-cluster \ --namespace ${NEBULA_CLUSTER_NAMESPACE} --create-namespace --version 0.1.0 \ --set nameOverride=${NEBULA_CLUSTER_NAME} \ --set nebula.storageClassName="${STORAGE_CLASS_NAME}" \ --set nebula.graphd.storage="${STORAGE_SIZE_GRAPHD}" \ --set nebula.metad.storage="${STORAGE_SIZE_METAD}" \ --set nebula.storaged.storage="${STORAGE_SIZE_STORAGED}" \ --set nebula.storaged.replicas=5# 稍等一会儿，检测 Nebula Cluster 是否启动失常$ kubectl -n ${NEBULA_CLUSTER_NAMESPACE} get nebulaclusterNAME GRAPHD-DESIRED GRAPHD-READY METAD-DESIRED METAD-READY STORAGED-DESIRED STORAGED-READY AGEnebula 2 2 3 3 5 5 6m12s$ kubectl -n ${NEBULA_CLUSTER_NAMESPACE} get podNAME READY STATUS RESTARTS AGEnebula-graphd-0 1/1 Running 0 2m30snebula-graphd-1 1/1 Running 0 2m30snebula-metad-0 1/1 Running 0 2m30snebula-metad-1 1/1 Running 0 2m30snebula-metad-2 1/1 Running 0 2m30snebula-storaged-0 1/1 Running 0 2m30snebula-storaged-1 1/1 Running 0 2m30snebula-storaged-2 1/1 Running 0 2m30snebula-storaged-3 1/1 Running 0 52snebula-storaged-4 1/1 Running 0 52s具体的装置阐明请见：应用 Helm 装置 Nebula Operator。
拜访 Nebula Cluster
终于，Nebula Cluster 启动胜利了，接下来开始拜访集群吧！
Kubernetes 外部拜访
首先，在 Kubernetes 中启动一个 Nebula Graph Console，执行命令如下：
$ cat <<EOF | kubectl apply -f -apiVersion: v1kind: Podmetadata: name: nebula-consolespec: containers: - name: nebula-console image: vesoft/nebula-console:v2-nightly command: - sleep - "1000000"EOF而后再通过方才创立的 Nebula Graph Console 来拜访集群，如下：
$ kubectl exec -it nebula-console -- \ nebula-console -u u -p p --addr ${NEBULA_CLUSTER_NAME}-graphd-svc.${NEBULA_CLUSTER_NAMESPACE}.svc --port 96692021/06/23 06:21:22 [INFO] connection pool is initialized successfullyWelcome to Nebula Graph!(u@nebula) [(none)]> show hosts+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| Host | Port | Status | Leader count | Leader distribution | Partition distribution |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-0.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-1.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-2.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-3.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-4.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "Total" | | | 0 | | |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+Got 4 rows (time spent 7669/9367 us)Wed, 23 Jun 2021 06:21:26 UTCKubernetes 内部拜访
Kubernetes 外部的服务在集群内部要想拜访，能够应用hostPort、hostNetwork、Ingress、LoadBalancer等。这里利用云厂商的便利性，间接应用LoadBalancer来拜访集群。
留神：此办法会裸露你的 Nebula 集群，请勿在生产环境应用。
首先，将Graphd Service的type改成LoadBalancer，而后再查看EXTERNAL-IP。
# 将 service 的 type 改成 LoadBalancer$ kubectl patch -n ${NEBULA_CLUSTER_NAMESPACE} svc ${NEBULA_CLUSTER_NAME}-graphd-svc \ -p '{"spec": {"type": "LoadBalancer"}}'# 获取 EXTERNAL-IP ，如果为 pending ，请稍等一会儿再重试$ kubectl -n ${NEBULA_CLUSTER_NAMESPACE} get svc nebula-graphd-svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGEnebula-graphd-svc LoadBalancer 172.16.85.222 x.x.x.x 9669:31460/TCP,19669:32579/TCP,19670:31481/TCP 27m当初，能够依据EXTERNAL-IP来拜访集群了，比方此处为x.x.x.x。
$ export EXTERNAL_IP=x.x.x.x$ docker run -it --rm vesoft/nebula-console:v2-nightly -u u -p p --addr ${EXTERNAL_IP} --port 96692021/06/23 06:42:17 [INFO] connection pool is initialized successfullyWelcome to Nebula Graph!(u@nebula) [(none)]> show hosts+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| Host | Port | Status | Leader count | Leader distribution | Partition distribution |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-0.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-1.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-2.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-3.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "nebula-storaged-4.nebula-storaged-headless.nebula.svc.cluster.local" | 9779 | "ONLINE" | 0 | "No valid partition" | "No valid partition" |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+| "Total" | | | 0 | | |+-----------------------------------------------------------------------+------+----------+--------------+----------------------+------------------------+Got 4 rows (time spent 3747/60433 us)Wed, 23 Jun 2021 06:42:21 UTC享受工夫
功败垂成！
纵情地在 Nebula Graph 中驰骋吧！