Kubernetes使用etcd来存储集群的实时运行数据(如节点状态信息),而其它pod都是无状态的、能够根据负载调度,在多个节点(node)间进行漂移。etcd自己是能够部署为无中心的多节点互备集群,从而消除整个集群的单一故障点。在kubeadm的缺省部署下,只在master上运行一个etcd实例(etcd-xxx),可使用kubectl get pod -n kube-system 查看运行状态。html
下面咱们来探索一下kubernetes的etcd实例究竟是如何实现和管理的。在kubernetes的master节点上输入:node
kubectl describe pod/etcd-podc01 -n kube-system > etcd.txt
输出以下:docker
Name: etcd-podc01 Namespace: kube-system Priority: 2000000000 PriorityClassName: system-cluster-critical Node: podc01/10.1.1.181 Start Time: Mon, 03 Dec 2018 10:42:05 +0800 Labels: component=etcd tier=control-plane Annotations: kubernetes.io/config.hash: bcc0eea4c53f3b70d13b771ad88e31b7 kubernetes.io/config.mirror: bcc0eea4c53f3b70d13b771ad88e31b7 kubernetes.io/config.seen: 2018-12-05T11:05:31.8690622+08:00 kubernetes.io/config.source: file scheduler.alpha.kubernetes.io/critical-pod: Status: Running IP: 10.1.1.181 Containers: etcd: Container ID: docker://8f301c91902a9399f144943013166a09dd0766a9b96c26fe2d8e335418a55cab Image: k8s.gcr.io/etcd:3.2.24 Image ID: docker-pullable://registry.cn-hangzhou.aliyuncs.com/openthings/k8s-gcr-io-etcd@sha256:7b073bdab8c52dc23dfb3e2101597d30304437869ad8c0b425301e96a066c408 Port: <none> Host Port: <none> Command: etcd --advertise-client-urls=https://127.0.0.1:2379 --cert-file=/etc/kubernetes/pki/etcd/server.crt --client-cert-auth=true --data-dir=/var/lib/etcd --initial-advertise-peer-urls=https://127.0.0.1:2380 --initial-cluster=podc01=https://127.0.0.1:2380 --key-file=/etc/kubernetes/pki/etcd/server.key --listen-client-urls=https://127.0.0.1:2379 --listen-peer-urls=https://127.0.0.1:2380 --name=podc01 --peer-cert-file=/etc/kubernetes/pki/etcd/peer.crt --peer-client-cert-auth=true --peer-key-file=/etc/kubernetes/pki/etcd/peer.key --peer-trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt --snapshot-count=10000 --trusted-ca-file=/etc/kubernetes/pki/etcd/ca.crt State: Running Started: Wed, 05 Dec 2018 11:05:35 +0800 Ready: True Restart Count: 0 Liveness: exec [/bin/sh -ec ETCDCTL_API=3 etcdctl --endpoints=https://[127.0.0.1]:2379 --cacert=/etc/kubernetes/pki/etcd/ca.crt --cert=/etc/kubernetes/pki/etcd/healthcheck-client.crt --key=/etc/kubernetes/pki/etcd/healthcheck-client.key get foo] delay=15s timeout=15s period=10s #success=1 #failure=8 Environment: <none> Mounts: /etc/kubernetes/pki/etcd from etcd-certs (rw) /var/lib/etcd from etcd-data (rw) Conditions: Type Status Initialized True Ready True ContainersReady True PodScheduled True Volumes: etcd-data: Type: HostPath (bare host directory volume) Path: /var/lib/etcd HostPathType: DirectoryOrCreate etcd-certs: Type: HostPath (bare host directory volume) Path: /etc/kubernetes/pki/etcd HostPathType: DirectoryOrCreate QoS Class: BestEffort Node-Selectors: <none> Tolerations: :NoExecute Events: <none>
能够看到,etcd是使用的host-network网络,而后把系统参数和数据等都映射到了宿主机的目录(配置参数位于宿主机的/var/lib/etcd,证书文件位于/etc/kubernetes/pki/etcd)。数据库
在宿主机下输入 sudo ls -l /var/lib/etcd/member/snap 能够看到etcd服务所产生的快照文件,以下所示:api
supermap@podc01:~/openthings/kubernetes-tools/jupyter$ sudo ls -l /var/lib/etcd/member/snap 总用量 8924 -rw-r--r-- 1 root root 8160 12月 5 09:19 0000000000000005-00000000001fbdd0.snap -rw-r--r-- 1 root root 8160 12月 5 10:37 0000000000000005-00000000001fe4e1.snap -rw-r--r-- 1 root root 8508 12月 5 11:42 0000000000000006-0000000000200bf2.snap -rw-r--r-- 1 root root 8509 12月 5 12:49 0000000000000006-0000000000203303.snap -rw-r--r-- 1 root root 8509 12月 5 13:56 0000000000000006-0000000000205a14.snap -rw------- 1 root root 24977408 12月 5 14:13 db
查看etcd的证书文件:网络
supermap@podc01:~/openthings/kubernetes-tools/jupyter$ ls -l /etc/kubernetes/pki/etcd 总用量 32 -rw-r--r-- 1 root root 1017 11月 23 10:08 ca.crt -rw------- 1 root root 1679 11月 23 10:08 ca.key -rw-r--r-- 1 root root 1094 11月 23 10:08 healthcheck-client.crt -rw------- 1 root root 1679 11月 23 10:08 healthcheck-client.key -rw-r--r-- 1 root root 1127 11月 23 10:08 peer.crt -rw------- 1 root root 1679 11月 23 10:08 peer.key -rw-r--r-- 1 root root 1119 11月 23 10:08 server.crt -rw------- 1 root root 1675 11月 23 10:08 server.key
这些文件和从Kubernetes的pod命令行进去看到的是彻底同样的(原本就是同一个目录)。app
下一步,咱们来链接到这个实例,查看具体的运行信息。ui
首先,安装etcd-client,这是etcd的独立客户端。url
sudo apt install etcd-client
而后,链接到etcd实例(endpoints为上面所显示的地址参数:advertise-client-urls):spa
sudo etcdctl --endpoints https://127.0.0.1:2379 --cert-file=/etc/kubernetes/pki/etcd/server.crt --key-file=/etc/kubernetes/pki/etcd/server.key --ca-file=/etc/kubernetes/pki/etcd/ca.crt member list
我这里的输出为:
a874c87fd42044f: name=podc01 peerURLs=https://127.0.0.1:2380 clientURLs=https://127.0.0.1:2379 isLeader=true
能够照此输入其余命令,来访问由kubernetes所启动的实例(实际运行时由kubelet服务控制)。
知道了上面的秘密,备份etcd 就不难了。有三个办法:
sudo ETCDCTL_API=3 etcdctl snapshot save "/home/supermap/k8s-backup/data/etcd-snapshot/$(date +%Y%m%d_%H%M%S)_snapshot.db" --endpoints=127.0.0.1:2379 --cert="/etc/kubernetes/pki/etcd/server.crt" --key="/etc/kubernetes/pki/etcd/server.key" --cacert="/etc/kubernetes/pki/etcd/ca.crt"
使用kubernetes的cronjob实现按期自动化备份须要对images和启动参数有一些调整,我修改后的yaml文件以下:
apiVersion: batch/v1beta1 kind: CronJob metadata: name: etcd-disaster-recovery namespace: cronjob spec: schedule: "0 22 * * *" jobTemplate: spec: template: metadata: labels: app: etcd-disaster-recovery spec: affinity: nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: kubernetes.io/hostname operator: In values: - podc01 containers: - name: etcd image: k8s.gcr.io/etcd:3.2.24 imagePullPolicy: "IfNotPresent" command: - sh - -c - "export ETCDCTL_API=3; \ etcdctl --endpoints=$ENDPOINT \ --cert=/etc/kubernetes/pki/etcd/server.crt \ --key=/etc/kubernetes/pki/etcd/server.key \ --cacert=/etc/kubernetes/pki/etcd/ca.crt \ snapshot save /snapshot/$(date +%Y%m%d_%H%M%S)_snapshot.db; \ echo etcd backup success" env: - name: ENDPOINT value: "https://127.0.0.1:2379" volumeMounts: - mountPath: "/etc/kubernetes/pki/etcd" name: etcd-certs - mountPath: "/var/lib/etcd" name: etcd-data - mountPath: "/snapshot" name: snapshot subPath: data/etcd-snapshot - mountPath: /etc/localtime name: lt-config - mountPath: /etc/timezone name: tz-config restartPolicy: OnFailure volumes: - name: etcd-certs hostPath: path: /etc/kubernetes/pki/etcd - name: etcd-data hostPath: path: /var/lib/etcd - name: snapshot hostPath: path: /home/supermap/k8s-backup - name: lt-config hostPath: path: /etc/localtime - name: tz-config hostPath: path: /etc/timezone hostNetwork: true
除此以外,这样Kubernetes的etcd主数据库就备份完成了。
不过,完整地备份和恢复kubernetes集群还须要一些其它的操做,对于每个运行的应用都还须要执行单独的备份操做。