架构

  • 基于statefulset实现一主多从redis，动态扩缩容redis从库，并基于storageclass实现动态存储，保证数据的持久化存储

在这里插入图片描述

主机名IP
k8s-master-1192.168.0.10
k8s-node-1192.168.0.11
k8s-nfs192.168.0.55

nfs-provider

# k8s-nfs nfs配置信息
[root@k8s-nfs ~]# cat /etc/exports
/data	192.168.0.0/24(rw,all_squash)

[root@k8s-master-1 1master-Nslave]# cat nfs-provider.yaml 
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: redis
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-runner
rules:
  - apiGroups: [""]
    resources: ["nodes"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["persistentvolumes"]
    verbs: ["get", "list", "watch", "create", "delete"]
  - apiGroups: [""]
    resources: ["persistentvolumeclaims"]
    verbs: ["get", "list", "watch", "update"]
  - apiGroups: ["storage.k8s.io"]
    resources: ["storageclasses"]
    verbs: ["get", "list", "watch"]
  - apiGroups: [""]
    resources: ["events"]
    verbs: ["create", "update", "patch"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: run-nfs-client-provisioner
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: redis
roleRef:
  kind: ClusterRole
  name: nfs-client-provisioner-runner
  apiGroup: rbac.authorization.k8s.io
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: redis
rules:
  - apiGroups: [""]
    resources: ["endpoints"]
    verbs: ["get", "list", "watch", "create", "update", "patch"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: leader-locking-nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: redis
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: redis
roleRef:
  kind: Role
  name: leader-locking-nfs-client-provisioner
  apiGroup: rbac.authorization.k8s.io
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nfs-client-provisioner
  labels:
    app: nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: redis
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nfs-client-provisioner
  template:
    metadata:
      labels:
        app: nfs-client-provisioner
    spec:
      nodeName: k8s-master-1   #设置在master节点运行
      tolerations:             #设置容忍master节点污点
      - key: node-role.kubernetes.io/master
        operator: Equal
        value: "true"
      serviceAccountName: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          image: registry.cn-hangzhou.aliyuncs.com/jiayu-kubernetes/nfs-subdir-external-provisioner:v4.0.0
          imagePullPolicy: IfNotPresent
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: k8s/nfs-subdir-external-provisioner
            - name: NFS_SERVER
              value: 192.168.0.55
            - name: NFS_PATH
              value: /data
      volumes:
        - name: nfs-client-root
          nfs:
            server: 192.168.0.55  # NFS SERVER_IP
            path: /data
---
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: redis-nfs
  namespace: redis
  annotations:
    storageclass.kubernetes.io/is-default-class: "false"  # 是否设置为默认的storageclass
provisioner: k8s/nfs-subdir-external-provisioner # or choose another name, must match deployment's env PROVISIONER_NAME'
allowVolumeExpansion: true
reclaimPolicy: Delete
parameters:
  archiveOnDelete: "false"

redis.conf

[root@k8s-master-1 1master-Nslave]# cat configmap.yaml 
apiVersion: v1
kind: Namespace
metadata:
  name: redis
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: redis
  namespace: redis
data:
  redis.conf: |-
    daemonize no
    protected-mode no
    bind 0.0.0.0
    port 6379
    timeout 300
    databases 16
    save 900 1
    save 300 10
    save 60 10000 
    loglevel notice
    logfile /data/redis.log
    ###################    RDB        ####################
    dir /data
    stop-writes-on-bgsave-error yes
    rdbcompression yes
    dbfilename dump.rdb
    ##################     REPL       ################### 
    slave-read-only yes
    repl-diskless-sync no
    repl-timeout 120
    ##################    SECURITY    ###################
    requirepass 123456
    masterauth 123456
    ##################     AOF        ####################
    appendonly no
    appendfilename "appendonly.aof"
    appendfsync no

statefulset

[root@k8s-master-1 1master-Nslave]# cat statefulset.yaml 
apiVersion: v1
kind: Service
metadata:
  name: redis
  namespace: redis
spec:
  selector:
    app: redis
  ports:
  - name: redis
    port: 6379
    targetPort: 6379
    protocol: TCP
  clusterIP: None
  type: ClusterIP
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: redis
  namespace: redis
spec:
  replicas: 2                  				 # 默认是一主一从
  selector:
    matchLabels:
      app: redis
  serviceName: redis
  template:
    metadata:
      labels:
        app: redis
    spec:
      containers:
      - name: redis
        image: redis:5
        imagePullPolicy: IfNotPresent
        command:
        - /bin/sh
        - -c
        - |
          set -e
          hostname=$(echo `hostname` | grep -oE '\-([0-9]+)$')
          if [ "$hostname" != "-0" ]; then  #如果不是第一个节点，则向第一个节点同步
            redis-server  /etc/redis.conf slaveof redis-0.redis.redis.svc.cluster.local 6379
          else
            redis-server /etc/redis.conf
          fi
        volumeMounts:
        - name: redis-data
          mountPath: /data
        - name: redis-conf
          mountPath: /etc/redis.conf
          subPath: redis.conf
      volumes:
      - name: redis-conf
        configMap:
          name: redis
  volumeClaimTemplates:
  - metadata:
      name: redis-data
      namespace: redis
    spec:
      accessModes: ["ReadWriteMany"]
      storageClassName: redis-nfs
      resources:
        requests:
          storage: 500Mi

部署

# 部署configmap
[root@k8s-master-1 1master-Nslave]# kubectl apply -f configmap.yaml 
namespace/redis created
configmap/redis created

# 部署nfs-provider
[root@k8s-master-1 1master-Nslave]# kubectl apply -f nfs-provider.yaml 
serviceaccount/nfs-client-provisioner created
clusterrole.rbac.authorization.k8s.io/nfs-client-provisioner-runner created
clusterrolebinding.rbac.authorization.k8s.io/run-nfs-client-provisioner created
role.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created
rolebinding.rbac.authorization.k8s.io/leader-locking-nfs-client-provisioner created
deployment.apps/nfs-client-provisioner created
storageclass.storage.k8s.io/redis-nfs created

# 部署statefulset
[root@k8s-master-1 1master-Nslave]# kubectl apply -f statefulset.yaml 
service/redis created
statefulset.apps/redis created

# 查看pod
[root@k8s-master-1 1master-Nslave]# kubectl get pods -n redis
NAME                                      READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-7f6758d967-l9b5p   1/1     Running   0          2m10s
redis-0                                   1/1     Running   0          100s
redis-1                                   1/1     Running   0          53s

# 查看PV，PVC
[root@k8s-master-1 1master-Nslave]# kubectl get pvc -n redis
NAME                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
redis-data-redis-0   Bound    pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            redis-nfs      2m21s
redis-data-redis-1   Bound    pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            redis-nfs      94s
[root@k8s-master-1 1master-Nslave]# kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                      STORAGECLASS   REASON   AGE
pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            Delete           Bound    redis/redis-data-redis-1   redis-nfs               96s
pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            Delete           Bound    redis/redis-data-redis-0   redis-nfs               2m23s


# k8s-nfs节点查看
[root@k8s-nfs ~]# ls /data
redis-redis-data-redis-0-pvc-e0642424-f6b3-405f-9d12-d53b277be042  redis-redis-data-redis-1-pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6


# 查看redis-1复制情况
[root@k8s-master-1 1master-Nslave]# kubectl exec redis-1 -n redis -- redis-cli -a 123456 info replication
# Replication
role:slave  #从库
master_host:redis-0.redis.redis.svc.cluster.local  #主库信息
master_port:6379
master_link_status:up
master_last_io_seconds_ago:7
master_sync_in_progress:0
slave_repl_offset:252
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:03c3dd18042139cbe116946f6c46c640fb91681b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:252
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:1
repl_backlog_histlen:252

扩容

扩容从redis-0->redis-N

# 扩容
[root@k8s-master-1 1master-Nslave]# kubectl scale statefulset redis --replicas=4 -n redis
statefulset.apps/redis scaled

# 查看pod
[root@k8s-master-1 1master-Nslave]# kubectl get pods -n redis
NAME                                      READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-7f6758d967-l9b5p   1/1     Running   0          6m52s
redis-0                                   1/1     Running   0          6m22s
redis-1                                   1/1     Running   0          5m35s
redis-2                                   1/1     Running   0          16s
redis-3                                   1/1     Running   0          11s

# 可见pvc,pv都是动态生成的
[root@k8s-master-1 1master-Nslave]# kubectl get pvc -n redis
NAME                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
redis-data-redis-0   Bound    pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            redis-nfs      7m
redis-data-redis-1   Bound    pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            redis-nfs      6m13s
redis-data-redis-2   Bound    pvc-521d77ec-64df-44e1-8a49-22d032046b86   500Mi      RWX            redis-nfs      54s
redis-data-redis-3   Bound    pvc-365be101-2ced-4800-9db0-be68fdedd64d   500Mi      RWX            redis-nfs      49s
[root@k8s-master-1 1master-Nslave]# kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                      STORAGECLASS   REASON   AGE
pvc-365be101-2ced-4800-9db0-be68fdedd64d   500Mi      RWX            Delete           Bound    redis/redis-data-redis-3   redis-nfs               55s
pvc-521d77ec-64df-44e1-8a49-22d032046b86   500Mi      RWX            Delete           Bound    redis/redis-data-redis-2   redis-nfs               60s
pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            Delete           Bound    redis/redis-data-redis-1   redis-nfs               6m19s
pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            Delete           Bound    redis/redis-data-redis-0   redis-nfs               7m6s

# 查看复制信息，可见同步正常
[root@k8s-master-1 1master-Nslave]# kubectl exec redis-3 -n redis -- redis-cli -a 123456 info replication
# Replication
role:slave
master_host:redis-0.redis.redis.svc.cluster.local
master_port:6379
master_link_status:up
master_last_io_seconds_ago:1
master_sync_in_progress:0
slave_repl_offset:630
slave_priority:100
slave_read_only:1
connected_slaves:0
master_replid:03c3dd18042139cbe116946f6c46c640fb91681b
master_replid2:0000000000000000000000000000000000000000
master_repl_offset:630
second_repl_offset:-1
repl_backlog_active:1
repl_backlog_size:1048576
repl_backlog_first_byte_offset:449
repl_backlog_histlen:182
Warning: Using a password with '-a' or '-u' option on the command line interface may not be safe.

缩容

缩容从redis-N->redis-0

# 缩容
[root@k8s-master-1 1master-Nslave]# kubectl scale statefulset redis --replicas=1 -n redis
statefulset.apps/redis scaled

# 查看pod
[root@k8s-master-1 1master-Nslave]# kubectl get pods -n redis
NAME                                      READY   STATUS    RESTARTS   AGE
nfs-client-provisioner-7f6758d967-l9b5p   1/1     Running   0          11m
redis-0                                   1/1     Running   0          11m


# 查看pv，pvc，可见即使pod被删除了pvc和pv都没有被删除，后续当我们再进行扩容时对应的pod还是会使用之前的pv，
[root@k8s-master-1 1master-Nslave]# kubectl get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                      STORAGECLASS   REASON   AGE
pvc-365be101-2ced-4800-9db0-be68fdedd64d   500Mi      RWX            Delete           Bound    redis/redis-data-redis-3   redis-nfs               6m29s
pvc-521d77ec-64df-44e1-8a49-22d032046b86   500Mi      RWX            Delete           Bound    redis/redis-data-redis-2   redis-nfs               6m34s
pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            Delete           Bound    redis/redis-data-redis-1   redis-nfs               11m
pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            Delete           Bound    redis/redis-data-redis-0   redis-nfs               12m
[root@k8s-master-1 1master-Nslave]# kubectl get pvc -n redis
NAME                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
redis-data-redis-0   Bound    pvc-e0642424-f6b3-405f-9d12-d53b277be042   500Mi      RWX            redis-nfs      12m
redis-data-redis-1   Bound    pvc-5925df68-31da-41c9-9655-7e9bd4c9bfb6   500Mi      RWX            redis-nfs      11m
redis-data-redis-2   Bound    pvc-521d77ec-64df-44e1-8a49-22d032046b86   500Mi      RWX            redis-nfs      6m39s
redis-data-redis-3   Bound    pvc-365be101-2ced-4800-9db0-be68fdedd64d   500Mi      RWX            redis-nfs      6m34s
# linux # 运维 # k8s # docker
Logo
K8S/Kubernetes

K8S/Kubernetes社区为您提供最前沿的新闻资讯和知识内容

更多推荐

【深度】阿里巴巴万级规模 K8s 集群全局高可用体系之美

作者 |  韩堂、柘远、沉醉来源 | 阿里巴巴云原生公众号​前言台湾作家林清玄在接受记者采访的时候，如此评价自己 30 多年写作生涯：“第一个十年我才华横溢，‘贼光闪现’，令周边黯然失色；第二个十年，我终于‘宝光现形’，不再去抢风头，反而与身边的美丽相得益彰；进入第三个十年，繁华落尽见真醇，我进入了‘醇光初现’的阶段，真正体味到了境界之美”。​长夜有穷，真水无香。领略过了 K8s“身在江

avatar K8S/Kubernetes

如何基于 K8s 构建下一代 DevOps 平台？

作者 | 孙健波（天元）导读：当前云原生 DevOps 体系现状如何？面临哪些挑战？如何通过 OAM 解决云原生 DevOps 场景下的诸多问题？云原生开发应用模型 OAM(Open Application Model) 社区核心成员孙健波将为大家一一解答，并分享如何基于 OAM 和 Kubernetes 打造无限能力的下一代 DevOps 平台。什么是 DevOps？为什么基于 Kub

avatar K8S/Kubernetes

k8s 火了！

2020，上云之年，产品云端化成为一种趋势。在一线城市，很多公司都已经构建了自己的私有云环境，比如阿里云、网易云、华为云等。而Kubernetes 作为基于容器编排领域的王者，具备扩展...

avatar K8S/Kubernetes