YAML file (Apache 2.0 source, distributed as Docker image) ClickHouse cluster resources kubectl apply create resources What does ClickHouse look like on Kubernetes? Shard 1 Replica 1 https://github.com/Altinity/clickhouse-operator Install the operator: kubectl apply -f clickhouse-operator-install.yaml or: kubectl apply -f https://raw.githubusercontent.com/Altinity/ clickhouse-op See examples in later slides for storage definition kubectl is our tool $ kubectl create namespace demo namespace/demo created $ kubectl apply -f docs/examples/demo-01.yaml -n demo clickhouseinstallation

https://github.com/Altinity/clickhouse-operator Install the operator: kubectl apply -f clickhouse-operator-install.yaml or: kubectl apply -f https://raw.githubusercontent.com/Altinity/ clickhouse-op See examples in later slides for storage definition kubectl is our tool $ kubectl create namespace demo namespace/demo created $ kubectl apply -f docs/examples/demo-01.yaml -n demo clickhouseinstallation clickhouseinstallation.clickhouse.altinity.com/demo-01 created $ kubectl get all -n demo NAME READY STATUS RESTARTS AGE pod/chi-a82946-2946-0-0-0 1/1 Running 0

目录下执行如下命令： 1. export KKZONE=cn 2. ./kk create cluster -f config-sample.yaml -a artifact.tar.gz 3. kubectl get pod -A 2.10 安装 helm-push 插件 在 master 节点的 piedbinstaller 目录下执行如下命令： 1. helm env|grep yaml 的 error 报错可以忽略 可在 harbor 界面查看 helm chart 是否推送成功： 2.12 环境检查和准备 K8S 环境检查： 1. kubectl get nodes -l node-role.kubernetes.io/control- plane| awk '{print $1}' 请创建文件目录后再进行部署。 如下： 1. /var/lib/minio/data /var /lib/postgresql/data 在 master 节点检查 PV： 1. kubectl get pv 如果存在 pv-fdb, pv-etcd, pv-minio, pv-postgres，请务必在运行脚本前删除它们： 1. kubectl delete pv pv-fdb pv-minio pv-postgres pv-etcd 2.13

things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl 3. Install Helm 3: wget https://get.helm.sh/helm-v3.2.1-linux-amd64.tar.gz tar -xzf helm-v3.* # SUITE: None NOTES: Release name: vitess To access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces

things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl 3. Install Helm 3: wget https://get.helm.sh/helm-v3.2.1-linux-amd64.tar.gz tar -xzf helm-v3.* # SUITE: None NOTES: Release name: vitess To access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces

things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl 3. Install Helm 3: wget https://get.helm.sh/helm-v3.2.1-linux-amd64.tar.gz tar -xzf helm-v3.* # SUITE: None NOTES: Release name: vitess To access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces

things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl 3. Install Helm 3: wget https://get.helm.sh/helm-v3.2.1-linux-amd64.tar.gz tar -xzf helm-v3.* # SUITE: None NOTES: Release name: vitess To access administrative web pages, start a proxy with: kubectl proxy --port=8001 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namespaces

things out of the way: 1. Install Minikube and start a Minikube engine: minikube start 2. Install kubectl and ensure it is in your PATH. For example, on Linux: curl -LO https://storage.googleapis.com/kubernetes -release/release/`curl -s https://storage.googleapis.com/kubernetes -release/release/stable.txt`/bin/linux/amd64/kubectl 3. Install Helm 3: wget https://get.helm.sh/helm-v3.2.1-linux-amd64.tar.gz tar -xzf helm-v3.* # SUITE: None NOTES: Release name: vitess To access administrative web pages, start a proxy with: kubectl proxy --port=8001 74 Then use the following URLs: vtctld: http://localhost:8001/api/v1/namesp

installed on your local machine. kubectl You need a Kubernetes . Use the local one or consult your administrator for access. configuration file Setting up Kubernetes Kubectl settings Testing port forwarding differ in managed Kubernetes environments. Obtain the correct default namespace from your config. kubectl DBeaver User Guide 23.2. Page 360 of 700. Resource By clicking the button next to the field Kubernetes port forwarding by using . kubectl Tip: When clicking the dropdown menus in and , you can select settings directly from your Context Namespace config. kubectl The Kubernetes Command-Line Tool

cluster deploy tidb-test v5.2.2 ./topology.yaml tiup $ kubectl apply -f tidb_cluster.yaml tidb-operator tiup cluster deploy 相当のことは kubectl apply 等で TidbCluster のリソースを定義 するだけで OK クラスター名やバージョンも TidbCluster もしくは下記のリポジトリから手動でインストールすることもできます 別途 CRD も必要になりますので、kubectl で作成しておきます https://github.com/pingcap/advanced-statefulset/blob/master/manifests/deployment.yaml $ kubectl apply -f https://raw.githubusercontent.com