[kubernetes]-笔记-使用rook-cepth作为mysql主从的存储

Dear 丶 2023-01-14 10:59 136阅读 0赞

##### 文件下载路径 #####

链接: https://pan.baidu.com/s/1j8liEMtaNQKcNQySbsNQhA 密码: crhl

##### 创建rook-ceph #####

cd /srv/stuy/k201-master/3.Kubernetes容器持久化存储/config/ceph
    kubectl create ns rook-ceph
    helm install rook-ceph rook-ceph -n rook-ceph
    kubectl --namespace rook-ceph get pods -l "app=rook-ceph-operator" -w

![562caec9bacb75cdd0c61693003da953.png][]

kubectl get pods -n rook-ceph

![6f485fd6949a4d812c349bab103d9cd1.png][]

配置文件cluster.yaml

#################################################################################################################
    # Define the settings for the rook-ceph cluster with common settings for a production cluster.
    # All nodes with available raw devices will be used for the Ceph cluster. At least three nodes are required
    # in this example. See the documentation for more details on storage settings available.
    
    # For example, to create the cluster:
    #   kubectl create -f common.yaml
    #   kubectl create -f operator.yaml
    #   kubectl create -f cluster.yaml
    #################################################################################################################
    
    apiVersion: ceph.rook.io/v1
    kind: CephCluster
    metadata:
      name: rook-ceph
      namespace: rook-ceph
    spec:
      cephVersion:
        # The container image used to launch the Ceph daemon pods (mon, mgr, osd, mds, rgw).
        # v12 is luminous, v13 is mimic, and v14 is nautilus.
        # RECOMMENDATION: In production, use a specific version tag instead of the general v14 flag, which pulls the latest release and could result in different
        # versions running within the cluster. See tags available at https://hub.docker.com/r/ceph/ceph/tags/.
        image: ceph/ceph:v14.2.1-20190430
        # Whether to allow unsupported versions of Ceph. Currently luminous, mimic and nautilus are supported, with the recommendation to upgrade to nautilus.
        # Do not set to true in production.
        allowUnsupported: false
      # The path on the host where configuration files will be persisted. Must be specified.
      # Important: if you reinstall the cluster, make sure you delete this directory from each host or else the mons will fail to start on the new cluster.
      # In Minikube, the '/data' directory is configured to persist across reboots. Use "/data/rook" in Minikube environment.
      dataDirHostPath: /var/lib/rook
      # set the amount of mons to be started
      mon:
        count: 3
        allowMultiplePerNode: false
      # enable the ceph dashboard for viewing cluster status
      dashboard:
        enabled: true
        # serve the dashboard under a subpath (useful when you are accessing the dashboard via a reverse proxy)
        # urlPrefix: /ceph-dashboard
        # serve the dashboard at the given port.
        # port: 8443
        # serve the dashboard using SSL
        # ssl: true
      network:
        # toggle to use hostNetwork
        hostNetwork: false
      rbdMirroring:
        # The number of daemons that will perform the rbd mirroring.
        # rbd mirroring must be configured with "rbd mirror" from the rook toolbox.
        workers: 0
      # To control where various services will be scheduled by kubernetes, use the placement configuration sections below.
      # The example under 'all' would have all services scheduled on kubernetes nodes labeled with 'role=storage-node' and
      # tolerate taints with a key of 'storage-node'.
    #  placement:
    #    all:
    #      nodeAffinity:
    #        requiredDuringSchedulingIgnoredDuringExecution:
    #          nodeSelectorTerms:
    #          - matchExpressions:
    #            - key: role
    #              operator: In
    #              values:
    #              - storage-node
    #      podAffinity:
    #      podAntiAffinity:
    #      tolerations:
    #      - key: storage-node
    #        operator: Exists
    # The above placement information can also be specified for mon, osd, and mgr components
    #    mon:
    #    osd:
    #    mgr:
      annotations:
    #    all:
    #    mon:
    #    osd:
    # If no mgr annotations are set, prometheus scrape annotations will be set by default.
    #   mgr:
      resources:
    # The requests and limits set here, allow the mgr pod to use half of one CPU core and 1 gigabyte of memory
    #    mgr:
    #      limits:
    #        cpu: "500m"
    #        memory: "1024Mi"
    #      requests:
    #        cpu: "500m"
    #        memory: "1024Mi"
    # The above example requests/limits can also be added to the mon and osd components
    #    mon:
    #    osd:
      storage: # cluster level storage configuration and selection
        useAllNodes: false
        useAllDevices: false
        deviceFilter:
        location:
        config:
          # The default and recommended storeType is dynamically set to bluestore for devices and filestore for directories.
          # Set the storeType explicitly only if it is required not to use the default.
          # storeType: bluestore
          # metadataDevice: "md0" # specify a non-rotational storage so ceph-volume will use it as block db device of bluestore.
          # databaseSizeMB: "1024" # uncomment if the disks are smaller than 100 GB
          # journalSizeMB: "1024"  # uncomment if the disks are 20 GB or smaller
          # osdsPerDevice: "1" # this value can be overridden at the node or device level
          # encryptedDevice: "true" # the default value for this option is "false"
    # Cluster level list of directories to use for filestore-based OSD storage. If uncommented, this example would create an OSD under the dataDirHostPath.
        #directories:
        #- path: /var/lib/rook
    # Individual nodes and their config can be specified as well, but 'useAllNodes' above must be set to false. Then, only the named
    # nodes below will be used as storage resources.  Each node's 'name' field should match their 'kubernetes.io/hostname' label.
        nodes:
        - name: "k8s-s001"
          devices:
          - name: vdc
        - name: "k8s-s002"
          devices:
          - name: vdc
        - name: "k8s-s003"
          devices:
          - name: vdc
    #    - name: "172.17.4.101"
    #      directories: # specific directories to use for storage can be specified for each node
    #      - path: "/rook/storage-dir"
    #      resources:
    #        limits:
    #          cpu: "500m"
    #          memory: "1024Mi"
    #        requests:
    #          cpu: "500m"
    #          memory: "1024Mi"
    #    - name: "172.17.4.201"
    #      devices: # specific devices to use for storage can be specified for each node
    #      - name: "sdb"
    #      - name: "nvme01" # multiple osds can be created on high performance devices
    #        config:
    #          osdsPerDevice: "5"
    #      config: # configuration can be specified at the node level which overrides the cluster level config
    #        storeType: filestore
    #    - name: "172.17.4.301"
    #      deviceFilter: "^sd."

##### 创建cepth集群 #####

kubectl apply -f cluster.yaml
    kubectl --namespace rook-ceph get pods -o wide -w

创建storageclass.yaml

---
    #################################################################################################################
    # Create a storage class with a pool that sets replication for a production environment.
    # A minimum of 3 nodes with OSDs are required in this example since the default failureDomain is host.
    #  kubectl create -f storageclass.yaml
    #################################################################################################################
    
    apiVersion: ceph.rook.io/v1
    kind: CephBlockPool
    metadata:
      name: replicapool
      namespace: rook-ceph
    spec:
      replicated:
        size: 3
    ---
    apiVersion: storage.k8s.io/v1
    kind: StorageClass
    metadata:
       name: rook-ceph-block
    provisioner: ceph.rook.io/block
    parameters:
      blockPool: replicapool
      # Specify the namespace of the rook cluster from which to create volumes.
      # If not specified, it will use `rook` as the default namespace of the cluster.
      # This is also the namespace where the cluster will be
      clusterNamespace: rook-ceph
      # Specify the filesystem type of the volume. If not specified, it will use `ext4`.
      fstype: xfs
      # (Optional) Specify an existing Ceph user that will be used for mounting storage with this StorageClass.
      #mountUser: user1
      # (Optional) Specify an existing Kubernetes secret name containing just one key holding the Ceph user secret.
      # The secret must exist in each namespace(s) where the storage will be consumed.
      #mountSecret: ceph-user1-secret

kubectl apply -f storageclass.yaml
    kubectl get storageclass

##### 用ceph作为mysql主从的存储 #####

kubectl apply -f mysql/

[562caec9bacb75cdd0c61693003da953.png]: /images/20221022/2098a268c82449aeb6dd9726cfa59f22.png
[6f485fd6949a4d812c349bab103d9cd1.png]: /images/20221022/4ac55cb555394b2ea350a87cebe43283.png