修改build地址
root@master:/opt/k8s-data/dockerfile/linux37/redis# vim build-command.sh 
#!/bin/bash
TAG=$1
docker build -t harbor.wyh.net/linux37/redis:${TAG} .
sleep 3
docker push  harbor.wyh.net/linux37/redis:${TAG}

修改基礎(chǔ)鏡像地址
root@master:/opt/k8s-data/dockerfile/linux37/redis# vim Dockerfile 
#JDK Base Image
FROM harbor.wyh.net/baseimages/centos:7.6.18102
MAINTAINER zhangshijie "zhangshijie@magedu.net"
ADD redis-4.0.14.tar.gz /usr/local/src
RUN ln -sv /usr/local/src/redis-4.0.14 /usr/local/redis && cd /usr/local/redis && make && cp src/redis-cli /usr/sbin/ && cp src/redis-server  /usr/sbin/ && mkdir -pv /data/redis-data
ADD redis.conf /usr/local/redis/redis.conf
ADD run_redis.sh /usr/local/redis/run_redis.sh
EXPOSE 6379
CMD ["/usr/local/redis/run_redis.sh"]

root@master:/opt/k8s-data/dockerfile/linux37/redis# bash build-command.sh v4.0.14
啟動(dòng)radis
root@master:/opt/k8s-data/dockerfile/linux37/redis# docker run -it --rm  harbor.magedu.net/linux37/redis:v4.0.14
root@haproxy1:~# mkdir /data/k8sdata/linux37/redis-datadir-1
修改redis的pv地址和數(shù)據(jù)存放路徑
root@master:/opt/k8s-data/yaml/linux37/redis/pv# vim redis-persistentvolume.yaml 

---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: redis-datadir-pv-1
  namespace: linux37
spec:
  capacity:
    storage: 10Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/k8sdata/linux37/redis-datadir-1
    server: 192.168.200.201
查看pvc
root@master:/opt/k8s-data/yaml/linux37/redis/pv# vim redis-persistentvolumeclaim.yaml 
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: redis-datadir-pvc-1
  namespace: linux37
spec:
  volumeName: redis-datadir-pv-1
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
創(chuàng)建pv
root@master:/opt/k8s-data/yaml/linux37/redis/pv# kubectl apply -f redis-persistentvolume.yaml 
查看pv，但是還沒有綁定pvc
root@master:/opt/k8s-data/yaml/linux37/redis/pv# kubectl get pv -n linux37
NAME                     CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS      CLAIM                             STORAGECLASS   REASON   AGE
redis-datadir-pv-1       10Gi       RWO            Retain           Available                                                             19s
創(chuàng)建pvc
root@master:/opt/k8s-data/yaml/linux37/redis/pv# kubectl apply -f redis-persistentvolumeclaim.yaml 
查看剛創(chuàng)建的pvc
root@master:/opt/k8s-data/yaml/linux37/redis/pv# kubectl get pvc -n linux37
NAME                      STATUS   VOLUME                   CAPACITY   ACCESS MODES   STORAGECLASS   AGE
redis-datadir-pvc-1       Bound    redis-datadir-pv-1       10Gi       RWO                           34s
查看pv已經(jīng)綁定在pvc上了
root@master:/opt/k8s-data/yaml/linux37/redis/pv# kubectl get pv -n linux37

NAME                     CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                             STORAGECLASS   REASON   AGE
redis-datadir-pv-1       10Gi       RWO            Retain           Bound    linux37/redis-datadir-pvc-1                               2m29s
root@master:/opt/k8s-data/yaml/linux37/redis# vim redis.yaml 
          image: harbor.wyh.net/linux37/redis:v4.0.14
修改鏡像地址
創(chuàng)建server
root@master:/opt/k8s-data/yaml/linux37/redis# kubectl apply -f redis.yaml 
查看pod是在哪個(gè)node節(jié)點(diǎn)的,是哪個(gè)node節(jié)點(diǎn)就用哪個(gè)node節(jié)點(diǎn)映射的ip地址
root@master:/opt/k8s-data/yaml/linux37/redis# kubectl get pod -n linux37 -o wide
NAME                                              READY   STATUS        RESTARTS   AGE   IP               NODE              NOMINATED NODE   READINESS GATES
deploy-devops-redis-d567d7694-sb2fm               1/1     Running       0          25m   172.31.167.112   192.168.200.206   <none>           <none>


進(jìn)入到容器里查看是否生效

root@master:/opt/k8s-data/yaml/linux37/redis# kubectl exec -it deploy-devops-redis-d567d7694-sb2fm bash -n linux37

image.png

添加一個(gè)key

key已經(jīng)添加進(jìn)去了

[root@deploy-devops-redis-d567d7694-sb2fm /]# redis-cli 
127.0.0.1:6379> AUTH 123456
OK
127.0.0.1:6379> keys *
1) "name"
127.0.0.1:6379> get name
"zhangsan"
查看redis存儲(chǔ)信息
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# cat appendonly.aof 
*2
$6
SELECT
$1
0
*3
$3
SET
$4
name
$8
zhangsan

刪除pod之后在，試試是否可以恢復(fù)

root@master:~# kubectl delete pod deploy-devops-redis-d567d7694-sb2fm -n linux37

驗(yàn)證Redis數(shù)據(jù)高可用：
刪除redis的pod，然后重新創(chuàng)建pod驗(yàn)證新生成的pod中是否有之前的數(shù)據(jù)，可能有丟失數(shù)據(jù)的幾率，取決于是否
開啟AOF或者dump數(shù)據(jù)的功能及設(shè)置

然后在次查看,由于是后端存儲(chǔ)所以信息沒有丟失，就是pod被刪除了，也可以通過后端存儲(chǔ)調(diào)用

root@master:~# kubectl exec -it deploy-devops-redis-d567d7694-wd7p5 bash -n linux37
[root@deploy-devops-redis-d567d7694-wd7p5 /]# redis-cli 
127.0.0.1:6379> auth 123456
OK
127.0.0.1:6379> get key
(nil)
127.0.0.1:6379> keys *
1) "name"
127.0.0.1:6379> get name
"zhangsan"

StatefulSet

StatefulSet是為了解決有狀態(tài)服務(wù)的問題（對(duì)應(yīng)Deployments和ReplicaSets是為無狀態(tài)服務(wù)而設(shè)計(jì)），其應(yīng)用場(chǎng)景包括
?穩(wěn)定的持久化存儲(chǔ)，即Pod重新調(diào)度后還是能訪問到相同的持久化數(shù)據(jù)，基于PVC來實(shí)現(xiàn)
?穩(wěn)定的網(wǎng)絡(luò)標(biāo)志，即Pod重新調(diào)度后其PodName和HostName不變，基于Headless Service（即沒有Cluster IP的Service）來實(shí)現(xiàn)
?有序部署，有序擴(kuò)展，即Pod是有順序的，在部署或者擴(kuò)展的時(shí)候要依據(jù)定義的順序依次依次進(jìn)行（即從0到N-1，在下一個(gè)Pod運(yùn)行之前所有之前的Pod必須都是Running和Ready狀態(tài)），基于init containers來實(shí)現(xiàn)
?有序收縮，有序刪除（即從N-1到0）

從上面的應(yīng)用場(chǎng)景可以發(fā)現(xiàn)，StatefulSet由以下幾個(gè)部分組成：
?用于定義網(wǎng)絡(luò)標(biāo)志（DNS domain）的Headless Service
?用于創(chuàng)建PersistentVolumes的volumeClaimTemplates
?定義具體應(yīng)用的StatefulSet

StatefulSet中每個(gè)Pod的DNS格式為statefulSetName-{0..N-1}.serviceName.namespace.svc.cluster.local，其中
?serviceName為Headless Service的名字
?0..N-1為Pod所在的序號(hào)，從0開始到N-1
?statefulSetName為StatefulSet的名字
?namespace為服務(wù)所在的namespace，Headless Servic和StatefulSet必須在相同的namespace
?.cluster.local為Cluster Domain
具體參考
https://www.kubernetes.org.cn/statefulset

實(shí)戰(zhàn)案例之MySQL 主從架構(gòu)：
https://www.kubernetes.org.cn/statefulset
基于StatefulSet實(shí)現(xiàn)：
Pod調(diào)度運(yùn)行時(shí)，如果應(yīng)用不需要任何穩(wěn)定的標(biāo)示、有序的部署、刪除和擴(kuò)展，則應(yīng)該使用一組無狀態(tài)副本的控制
器來部署應(yīng)用，例如 Deployment 或 ReplicaSet更適合無狀態(tài)服務(wù)需求，而StatefulSet適合管理所有有狀態(tài)的服
務(wù)，比如MySQL、MongoDB集群等。
基于StatefulSet 實(shí)現(xiàn)的MySQL 一主多從架構(gòu)

image.png

StatefulSet本質(zhì)上是Deployment的一種變體，在v1.9版本中已成為GA版本，它為了解決有狀態(tài)服務(wù)的問題，
它所管理的Pod擁有固定的Pod名稱，啟停順序，在StatefulSet中，Pod名字稱為網(wǎng)絡(luò)標(biāo)識(shí)(hostname)，還必
須要用到共享存儲(chǔ)。
在Deployment中，與之對(duì)應(yīng)的服務(wù)是service，而在StatefulSet中與之對(duì)應(yīng)的headless service，
headless service，即無頭服務(wù)，與service的區(qū)別就是它沒有Cluster IP，解析它的名稱時(shí)將返回該
Headless Service對(duì)應(yīng)的全部Pod的Endpoint列表。
StatefulSet 特點(diǎn)：
-> 給每個(gè)pdo分配固定且唯一的網(wǎng)絡(luò)標(biāo)識(shí)符
-> 給每個(gè)pod分配固定且持久化的外部存儲(chǔ)
-> 對(duì)pod進(jìn)行有序的部署和擴(kuò)展
-> 對(duì)pod進(jìn)有序的刪除和終止
-> 對(duì)pod進(jìn)有序的自動(dòng)滾動(dòng)更新

StatefulSet的組成部分：
Headless Service：用來定義Pod網(wǎng)絡(luò)標(biāo)識(shí)( DNS domain)。
StatefulSet：定義具體應(yīng)用，有多少個(gè)Pod副本，并為每個(gè)Pod定義了一個(gè)域名。
volumeClaimTemplates： 存儲(chǔ)卷申請(qǐng)模板，創(chuàng)建PVC，指定pvc名稱大小，將自動(dòng)創(chuàng)建pvc，且pvc必須由存
儲(chǔ)類供應(yīng)

創(chuàng)建mysql數(shù)據(jù)目錄
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# mkdir /data/linux37/mysql-datadir-1
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# mkdir /data/linux37/mysql-datadir-2
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# mkdir /data/linux37/mysql-datadir-3
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# mkdir /data/linux37/mysql-datadir-4
root@haproxy1:/data/k8sdata/linux37/redis-datadir-1# mkdir /data/linux37/mysql-datadir-5


修改nfs地址
root@master:/opt/k8s-data/yaml/linux37/mysql/pv# cat mysql-persistentvolume.yaml 
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mysql-datadir-1
  namespace: linux37
spec:
  capacity:
    storage: 50Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/linux37/mysql-datadir-1
    server: 192.168.200.201 
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mysql-datadir-2
  namespace: linux37
spec:
  capacity:
    storage: 50Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/linux37/mysql-datadir-2
    server: 192.168.200.201 
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mysql-datadir-3
  namespace: linux37
spec:
  capacity:
    storage: 50Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/linux37/mysql-datadir-3
    server: 192.168.200.201
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mysql-datadir-4
  namespace: linux37
spec:
  capacity:
    storage: 50Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/linux37/mysql-datadir-4
    server: 192.168.200.201
---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: mysql-datadir-5
  namespace: linux37
spec:
  capacity:
    storage: 50Gi
  accessModes:
    - ReadWriteOnce
  nfs:
    path: /data/linux37/mysql-datadir-5
    server: 192.168.200.201
創(chuàng)建pv
root@master:/opt/k8s-data/yaml/linux37/mysql/pv# kubectl apply -f mysql-persistentvolume.yaml 

root@master:/opt/k8s-data/yaml/linux37/mysql/pv# kubectl get pv -n linux37 | grep mysql | wc -l
5
下載mysql5.7的鏡像
root@master:/opt/k8s-data/dockerfile# docker pull mysql:5.7
root@master:/opt/k8s-data/dockerfile# docker run --it --rm mysql:5.7 bash 
查看mysql版本
root@9589a9780c7e:/# mysql -V
mysql  Ver 14.14 Distrib 5.7.28, for Linux (x86_64) using  EditLine wrapper
打標(biāo)簽
root@master:~# docker tag mysql:5.7 harbor.wyh.net/linux37/mysql:5.27
root@master:~# docker  tag mysql:5.7 harbor.wyh.net/linux37/mysql:v5.7.27
上傳鏡像
root@master:~# docker push harbor.wyh.net/linux37/mysql:v5.7.27

準(zhǔn)備xtrabackup鏡像
root@master:~# docker tag registry.cn-hangzhou.aliyuncs.com/hxpdocker/xtrabackup:1.0 harbor.wyh.net/linux37/xtrabackup:1.0
root@master:~# docker push harbor.wyh.net/linux37/xtrabackup:1.0
修改鏡像地址
root@master:/opt/k8s-data/yaml/linux37/mysql# cat mysql-statefulset.yaml | grep ^[^#]
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: mysql
spec:
  selector:
    matchLabels:
      app: mysql
  serviceName: mysql
  replicas: 3
  template:
    metadata:
      labels:
        app: mysql
    spec:
      initContainers:
      - name: init-mysql
        image: harbor.wyh.net/linux37/mysql:v5.7.27 
        command:
        - bash
        - "-c"
        - |
          set -ex
          # Generate mysql server-id from pod ordinal index.
          [[ `hostname` =~ -([0-9]+)$ ]] || exit 1
          ordinal=${BASH_REMATCH[1]}
          echo [mysqld] > /mnt/conf.d/server-id.cnf
          # Add an offset to avoid reserved server-id=0 value.
          echo server-id=$((100 + $ordinal)) >> /mnt/conf.d/server-id.cnf
          # Copy appropriate conf.d files from config-map to emptyDir.
          if [[ $ordinal -eq 0 ]]; then
            cp /mnt/config-map/master.cnf /mnt/conf.d/
          else
            cp /mnt/config-map/slave.cnf /mnt/conf.d/
          fi
        volumeMounts:
        - name: conf
          mountPath: /mnt/conf.d
        - name: config-map
          mountPath: /mnt/config-map
      - name: clone-mysql
        image: harbor.wyh.net/linux37/xtrabackup:1.0 
        command:
        - bash
        - "-c"
        - |
          set -ex
          # Skip the clone if data already exists.
          [[ -d /var/lib/mysql/mysql ]] && exit 0
          # Skip the clone on master (ordinal index 0).
          [[ `hostname` =~ -([0-9]+)$ ]] || exit 1
          ordinal=${BASH_REMATCH[1]}
          [[ $ordinal -eq 0 ]] && exit 0
          # Clone data from previous peer.
          ncat --recv-only mysql-$(($ordinal-1)).mysql 3307 | xbstream -x -C /var/lib/mysql
          # Prepare the backup.
          xtrabackup --prepare --target-dir=/var/lib/mysql
        volumeMounts:
        - name: data
          mountPath: /var/lib/mysql
          subPath: mysql
        - name: conf
          mountPath: /etc/mysql/conf.d
      containers:
      - name: mysql
        image: harbor.wyh.net/linux37/mysql:v5.7.27 
        env:
        - name: MYSQL_ALLOW_EMPTY_PASSWORD
          value: "1"
        ports:
        - name: mysql
          containerPort: 3306
        volumeMounts:
        - name: data
          mountPath: /var/lib/mysql
          subPath: mysql
        - name: conf
          mountPath: /etc/mysql/conf.d
        resources:
          requests:
            cpu: 500m
            memory: 1Gi
        livenessProbe:
          exec:
            command: ["mysqladmin", "ping"]
          initialDelaySeconds: 30
          periodSeconds: 10
          timeoutSeconds: 5
        readinessProbe:
          exec:
            # Check we can execute queries over TCP (skip-networking is off).
            command: ["mysql", "-h", "127.0.0.1", "-e", "SELECT 1"]
          initialDelaySeconds: 5
          periodSeconds: 2
          timeoutSeconds: 1
      - name: xtrabackup
        image: harbor.wyh.net/linux37/xtrabackup:1.0 
        ports:
        - name: xtrabackup
          containerPort: 3307
        command:
        - bash
        - "-c"
        - |
          set -ex
          cd /var/lib/mysql
          # Determine binlog position of cloned data, if any.
          if [[ -f xtrabackup_slave_info ]]; then
            # XtraBackup already generated a partial "CHANGE MASTER TO" query
            # because we're cloning from an existing slave.
            mv xtrabackup_slave_info change_master_to.sql.in
            # Ignore xtrabackup_binlog_info in this case (it's useless).
            rm -f xtrabackup_binlog_info
          elif [[ -f xtrabackup_binlog_info ]]; then
            # We're cloning directly from master. Parse binlog position.
            [[ `cat xtrabackup_binlog_info` =~ ^(.*?)[[:space:]]+(.*?)$ ]] || exit 1
            rm xtrabackup_binlog_info
            echo "CHANGE MASTER TO MASTER_LOG_FILE='${BASH_REMATCH[1]}',\
                  MASTER_LOG_POS=${BASH_REMATCH[2]}" > change_master_to.sql.in
          fi
          # Check if we need to complete a clone by starting replication.
          if [[ -f change_master_to.sql.in ]]; then
            echo "Waiting for mysqld to be ready (accepting connections)"
            until mysql -h 127.0.0.1 -e "SELECT 1"; do sleep 1; done
            echo "Initializing replication from clone position"
            # In case of container restart, attempt this at-most-once.
            mv change_master_to.sql.in change_master_to.sql.orig
            mysql -h 127.0.0.1 <<EOF
          $(<change_master_to.sql.orig),
            MASTER_HOST='mysql-0.mysql',
            MASTER_USER='root',
            MASTER_PASSWORD='',
            MASTER_CONNECT_RETRY=10;
          START SLAVE;
          EOF
          fi
          # Start a server to send backups when requested by peers.
          exec ncat --listen --keep-open --send-only --max-conns=1 3307 -c \
            "xtrabackup --backup --slave-info --stream=xbstream --host=127.0.0.1 --user=root"
        volumeMounts:
        - name: data
          mountPath: /var/lib/mysql
          subPath: mysql
        - name: conf
          mountPath: /etc/mysql/conf.d
        resources:
          requests:
            cpu: 100m
            memory: 100Mi
      volumes:
      - name: conf
        emptyDir: {}
      - name: config-map
        configMap:
          name: mysql
  volumeClaimTemplates:
  - metadata:
      name: data
    spec:
      accessModes: ["ReadWriteOnce"]
      resources:
        requests:
          storage: 10Gi

root@master:/opt/k8s-data/yaml/linux37/mysql# kubectl apply -f .

鏡像準(zhǔn)備：
https://github.com/docker-library/ #github 下載地址
基礎(chǔ)鏡像準(zhǔn)備：

找鏡像地址

進(jìn)入到容器
mysql> root@master:/opt/k8s-data/yaml/linux37/mysql# kubectl exec -it mysql-0 bash
創(chuàng)建數(shù)據(jù)庫(kù)
mysql> create database linux37;
查看容器有掛載
root@mysql-1:/# df -h |grep 19
192.168.200.201:/data/linux37/mysql-datadir-5/mysql   98G  7.2G   86G   8% /var/lib/mysql

進(jìn)入到另一個(gè)容器里,查看數(shù)據(jù)是否同步,是一主兩從