使用Kind搭建本地k8s集群

• 2019 年 10 月 7 日
• 筆記

介紹

Kind 是 Kubernetes In Docker 的縮寫，是使用 Docker 容器部署 Kubernetes 的工具。也是官方推薦的搭建本地集群的工具。

安裝 Kind

$ curl -Lo ./kind https://github.com/kubernetes-sigs/kind/releases/download/v0.5.1/kind-$(uname)-amd64  $ chmod +x ./kind  $ sudo mv ./kind /usr/bin/

安裝 Docker

步驟略

安裝 kubectl

$ sudo yum install kubernetes-client    或    $ curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectl  $ chmod +x ./kubectl  $ sudo mv ./kubectl /usr/bin/kubectl

單節點集群

創建集群

$ sudo kind create cluster  Creating cluster "kind" ...   ? Ensuring node image (kindest/node:v1.15.3)   ? Preparing nodes   ? Creating kubeadm config   ? Starting control-plane   ? Installing CNI   ? Installing StorageClass  Cluster creation complete. You can now use the cluster with:    $ export KUBECONFIG="$(sudo kind get kubeconfig-path --name="kind")"    $ sudo kubectl cluster-info  Kubernetes master is running at https://127.0.0.1:34059  KubeDNS is running at https://127.0.0.1:34059/api/v1/proxy/namespaces/kube-system/services/kube-dns    To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

也可以使用下面命令來在創建集群的時候制定集群名稱。

$ sudo kind create cluster --name mycluster

查看集群

查看集群資訊

$ export KUBECONFIG="$(kind get kubeconfig-path --name="kind")"  $ sudo kubectl cluster-info  Kubernetes master is running at https://127.0.0.1:34059  KubeDNS is running at https://127.0.0.1:34059/api/v1/proxy/namespaces/kube-system/services/kube-dns    To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

查看集群節點資訊

$ sudo kubectl get nodes  NAME                 STATUS    AGE  kind-control-plane   Ready     1h

查看系統上的集群

$ sudo kind get clusters  kind

刪除集群

$ sudo kind delete cluster  Deleting cluster "kind" ...  $KUBECONFIG is still set to use /root/.kube/kind-config-kind even though that file has been deleted, remember to unset it

多節點集群

對於多節點集群的創建，需要通過使用配置文件的方式來創建。

配置文件

先創建一個 yaml 格式文件，文件名就叫 kind-config.yaml，內容如下：

kind: Cluster  apiVersion: kind.sigs.k8s.io/v1alpha3  kubeadmConfigPatches:  - |    apiVersion: kubeadm.k8s.io/v1beta2    kind: ClusterConfiguration    metadata:      name: config    networking:      serviceSubnet: 10.0.0.0/16  - |    apiVersion: kubeadm.k8s.io/v1beta2    kind: InitConfiguration    metadata:      name: config    networking:      serviceSubnet: 10.0.0.0/16  nodes:  - role: control-plane  - role: control-plane  - role: control-plane  - role: worker  - role: worker  - role: worker

創建集群

通過配置文件創建集群

$ sudo kind create cluster --name mycluster --config kind-config.yaml  Creating cluster "mycluster" ...   ✓ Ensuring node image (kindest/node:v1.15.3)   ✓ Preparing nodes   ✓ Configuring the external load balancer   ✓ Creating kubeadm config   ✓ Starting control-plane   ✓ Installing CNI   ✓ Installing StorageClass   ✓ Joining more control-plane nodes   ✓ Joining worker nodes  Cluster creation complete. You can now use the cluster with:    export KUBECONFIG="$(kind get kubeconfig-path --name="mycluster")"  kubectl cluster-info

查看集群

查看集群資訊

$ export KUBECONFIG="$(sudo kind get kubeconfig-path --name="mycluster")"  $ sudo kubectl cluster-info  Kubernetes master is running at https://127.0.0.1:33483  KubeDNS is running at https://127.0.0.1:33483/api/v1/proxy/namespaces/kube-system/services/kube-dns    To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.

查看集群節點

$ sudo kubectl get nodes  NAME                       STATUS    AGE  mycluster-control-plane    Ready     6m  mycluster-control-plane2   Ready     5m  mycluster-control-plane3   Ready     4m  mycluster-worker           Ready     4m  mycluster-worker2          Ready     4m  mycluster-worker3          Ready     4m  ​``` shell    查詢集群容器    ​``` shell  $ sudo docker ps  CONTAINER ID        IMAGE                                                                                          COMMAND                  CREATED             STATUS              PORTS                                  NAMES  93bb0d8df106        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes        42008/tcp, 127.0.0.1:42008->6443/tcp   mycluster-control-plane  2a1b67d11463        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes                                               mycluster-worker3  d7a8f74a9e95        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes                                               mycluster-worker  8d2aaa019a21        kindest/haproxy:2.0.0-alpine                                                                   "/docker-entrypoin..."   9 minutes ago       Up 9 minutes        33483/tcp, 127.0.0.1:33483->6443/tcp   mycluster-external-load-balancer  dd2fca2b2401        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes                                               mycluster-worker2  f47d3c836f85        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes        39892/tcp, 127.0.0.1:39892->6443/tcp   mycluster-control-plane3  5feeee745b06        kindest/node:v1.15.3@sha256:27e388752544890482a86b90d8ac50fcfa63a2e8656a96ec5337b902ec8e5157   "/usr/local/bin/en..."   9 minutes ago       Up 9 minutes        36154/tcp, 127.0.0.1:36154->6443/tcp   mycluster-control-plane2  4213abeebc6f        kindest/haproxy:2.0.0-alpine         

刪除集群

$ sudo kind delete cluster --name mycluster  Deleting cluster "mycluster" ...  $KUBECONFIG is still set to use /root/.kube/kind-config-mycluster even though that file has been deleted, remember to unset it