k8s部署tidb4.0集群和监控

最新推荐文章于 2024-07-30 00:00:00 发布

dz45693

最新推荐文章于 2024-07-30 00:00:00 发布

阅读量3.2k

点赞数

分类专栏： docker k8s

本文链接：https://blog.csdn.net/ma_jiang/article/details/114987918

版权

本文档详细介绍了如何在Kubernetes (k8s) 环境中使用Helm和持久化存储部署TiDB 4.0集群及其监控系统。首先，安装Helm客户端，创建持久化存储类，接着部署TiDB的CRD、Operator，然后配置并启动TiDB集群。在集群部署完成后，进行了初始化设置并部署了监控组件。尽管默认的Grafana访问方式受限，但通过ingress暴露了服务，可以使用特定域名访问TiDB的dashboard、Grafana和Prometheus。文章还提供了相关的参考资料链接。

摘要由CSDN通过智能技术生成

书接上文 K8S 的 Volume[本地磁盘] ，这里我用上文创建的Provisioner来运行tidb数据库。我自己的k8s有helm和持久化存储，直接开干

准备：

1.、安装 helm 客户端（master 节点我本机有了旧版本这里没有更新，新旧版本后面命令有点不同）

wget -c https://get.helm.sh/helm-v3.4.2-linux-amd64.tar.gz
tar -xf helm-v3.4.2-linux-amd64.tar.gz
cd linux-amd64/
chmod +x helm
cp -a helm /usr/local/bin/
helm version -c

2、创建持久化存储 local-volume-provisioner.yaml 内容如下：

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: "local-storage"
provisioner: "kubernetes.io/no-provisioner"
volumeBindingMode: "WaitForFirstConsumer"
 
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: local-provisioner-config
  namespace: kube-system
data:
  setPVOwnerRef: "true"
  nodeLabelsForPV: |
    - kubernetes.io/hostname
  storageClassMap: |
    local-storage:
      hostDir: /mnt/disks
      mountDir: /mnt/disks
---
apiVersion: apps/v1
kind: DaemonSet
metadata:
  name: local-volume-provisioner
  namespace: kube-system
  labels:
    app: local-volume-provisioner
spec:
  selector:
    matchLabels:
      app: local-volume-provisioner
  template:
    metadata:
      labels:
        app: local-volume-provisioner
    spec:
      serviceAccountName: local-storage-admin
      containers:
        - image: "quay.io/external_storage/local-volume-provisioner:v2.3.4"
          name: provisioner
          securityContext:
            privileged: true
          env:
          - name: MY_NODE_NAME
            valueFrom:
              fieldRef:
                fieldPath: spec.nodeName
          - name: MY_NAMESPACE
            valueFrom:
              fieldRef:
                fieldPath: metadata.namespace
          - name: JOB_CONTAINER_IMAGE
            value: "quay.io/external_storage/local-volume-provisioner:v2.3.4"
          resources:
            requests:
              cpu: 100m
              memory: 100Mi
            limits:
              cpu: 100m
              memory: 100Mi
          volumeMounts:
            - mountPath: /etc/provisioner/config
              name: provisioner-config
              readOnly: true
            # mounting /dev in DinD environment would fail
            # - mountPath: /dev
            #   name: provisioner-dev
            - mountPath: /mnt/disks
              name: local-disks
              mountPropagation: "HostToContainer"
      volumes:
        - name: provisioner-config
          configMap:
            name: local-provisioner-config
        # - name: provisioner-dev
        #   hostPath:
        #     path: /dev
        - name: local-disks
          hostPath:
            path: /mnt/disks
 
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: local-storage-a