K8s部署JeecgBoot微服务-编写资源清单文件

最新推荐文章于 2023-10-19 15:31:55 发布
最新推荐文章于 2023-10-19 15:31:55 发布
阅读量546 收藏 1
点赞数
分类专栏： k8s 文章标签： kubernetes 微服务 java
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/William_Franca/article/details/128917571
版权

使用K8s部署JeecgBoot微服务-资源清单篇

最终效果图

在这里插入图片描述
在这里插入图片描述

创建NFS存储的动态供给

NFS动态供给插件，配置NFS服务器

apiVersion: apps/v1
kind: Deployment
metadata:
  name: nfs-client-provisioner
  namespace: jeecg-boot
spec:
  replicas: 1
  strategy:
    type: Recreate
  selector:
    matchLabels:
      app: nfs-client-provisioner
  template:
    metadata:
      namespace: jeecg-boot
      labels:
        app: nfs-client-provisioner
    spec:
      serviceAccount: nfs-client-provisioner
      containers:
        - name: nfs-client-provisioner
          image: registry.cn-beijing.aliyuncs.com/pylixm/nfs-subdir-external-provisioner:v4.0.0
          volumeMounts:
            - name: nfs-client-root
              mountPath: /persistentvolumes
          env:
            - name: PROVISIONER_NAME
              value: k8s-sigs.io/nfs-subdir-external-provisioner
            - name: NFS_SERVER
              value: 192.168.0.2 #NFS服务器地址
            - name: NFS_PATH
              value: /opt  #NFS目录
      volumes:
        - name: nfs-client-root
          nfs:
            server: 192.168.0.2
            path: /opt

K8s的RBAC配置

apiVersion: v1
kind: ServiceAccount
metadata:
  name: nfs-client-provisioner
  # replace with namespace where provisioner is deployed
  namespace: jeecg-boot
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: nfs-client-provisioner-runner
rules:
  - 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: jeecg-boot
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: jeecg-boot
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: jeecg-boot
subjects:
  - kind: ServiceAccount
    name: nfs-client-provisioner
    # replace with namespace where provisioner is deployed
    namespace: jeecg-boot
roleRef:
  kind: Role
  name: leader-locking-nfs-client-provisioner
  apiGroup: rbac.authorization.k8s.io

创建存储类，名称为nfs-client（重要）

apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
  name: nfs-client
provisioner: k8s-sigs.io/nfs-subdir-external-provisioner # or choose another name, must match deployment's env PROVISIONER_NAME'
parameters:
  archiveOnDelete: "false"

NACOS使用外置的MYSQL数据库

创建字典信息

---
apiVersion: v1
data:
  mysql.db.name: nacos
  mysql.password: hsj@124Qk
  mysql.port: '3306'
  mysql.service.name: jeecg-boot-mysql
  mysql.user: root
  nacos.password: M2dAYN0sdk3c
kind: ConfigMap
metadata:
  name: nacos-cm
  namespace: jeecg-boot

MYSQL数据库IP为192.168.0.2

---
apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-mysql
  namespace: jeecg-boot              
  labels:
    name: jeecg-boot-mysql           
spec:
  clusterIP: None
  ports:
    - port: 3306
      name: jeecg-boot-mysql          
      targetPort: 3306
---
apiVersion: v1
kind: Endpoints
metadata:
  name: jeecg-boot-mysql
  namespace: jeecg-boot 
  labels:
    name: jeecg-boot-mysql
subsets:
  - addresses:
      - ip: 192.168.0.2        
    ports:
      - port: 3306

NACOS集群资源清单，暴露30848端口到公网

apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-nacos
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-nacos
spec:
  type: ClusterIP
  clusterIP: None
  ports:
    - port: 8848
      name: server
      targetPort: 8848
    - port: 9848
      name: client-rpc
      targetPort: 9848
    - port: 9849
      name: raft-rpc
      targetPort: 9849
    - port: 7848
      name: old-raft-rpc
      targetPort: 7848
  selector:
    app: nacos
---    
kind: Service
apiVersion: v1
metadata:
  labels:
    app: jeecg-boot-nacos
  name: nacos-cluster-manage
  namespace: jeecg-boot
spec:
  ports:
  - name: http
    port: 8848
    protocol: TCP
    targetPort: 8848
    nodePort: 30848
  selector:
    app: nacos
  type: NodePort 
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: nacos
  namespace: jeecg-boot
spec:
  serviceName: jeecg-boot-nacos
  replicas: 3
  template:
    metadata:
      labels:
        app: nacos
      annotations:
        pod.alpha.kubernetes.io/initialized: "true"
    spec:
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: "app"
                    operator: In
                    values:
                      - nacos
              topologyKey: "kubernetes.io/hostname"
      containers:
        - name: jeecg-boot-nacos
          image: "nacos/nacos-server:1.4.1"
          resources:
            requests:
              memory: "2Gi"
              cpu: "500m"
          ports:
            - containerPort: 8848
              name: client
            - containerPort: 9848
              name: client-rpc
            - containerPort: 9849
              name: raft-rpc
            - containerPort: 7848
              name: old-raft-rpc
          env:
            - name: NACOS_REPLICAS
              value: "3"
            - name: MYSQL_SERVICE_HOST
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.service.name
            - name: MYSQL_SERVICE_DB_NAME
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.db.name
            - name: MYSQL_SERVICE_PORT
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.port
            - name: MYSQL_SERVICE_USER
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.user
            - name: MYSQL_SERVICE_PASSWORD
              valueFrom:
                configMapKeyRef:
                  name: nacos-cm
                  key: mysql.password
            - name: NACOS_SERVER_PORT
              value: "8848"
            - name: NACOS_APPLICATION_PORT
              value: "8848"
            - name: PREFER_HOST_MODE
              value: "hostname"
            - name: NACOS_SERVERS
              value: "nacos-0.jeecg-boot-nacos.jeecg-boot.svc.cluster.local:8848 nacos-1.jeecg-boot-nacos.jeecg-boot.svc.cluster.local:8848 nacos-2.jeecg-boot-nacos.jeecg-boot.svc.cluster.local:8848" 
  selector:
    matchLabels:
      app: nacos

Redis的哨兵集群部署

apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-redis
  namespace: jeecg-boot
  labels:
    app: redis-sentinel
spec:
  ports:
    - name: redis-port
      port: 6379
      targetPort: 6379
      nodePort: 30637
  type: NodePort
  selector:
    app: redis-sentinel
---
apiVersion: v1
kind: Service
metadata:
  name: redis-sentinel
  namespace: jeecg-boot
  labels:
    app: redis-sentinel
spec:
  ports:
    - name: redis-port
      port: 26379
      targetPort: 26379
      nodePort: 30037
  type: NodePort
  selector:
    app: redis-sentinel
---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: redis
  namespace: jeecg-boot
spec:
  selector:
    matchLabels:
      app: redis-sentinel
  serviceName: "jeecg-boot-redis"
  replicas: 3
  template:
    metadata:
      labels:
        app: redis-sentinel
    spec:
      initContainers:
        - name: init-redis
          image: redis:5.0.7
          imagePullPolicy: IfNotPresent
          command:
            - bash
            - "-c"
            - |
              set -ex
              # Generate redis server-id from pod ordinal index.
              [[ `hostname` =~ -([0-9]+)$ ]] || exit 1
              ordinal=${BASH_REMATCH[1]}
              cat /mnt/config-map/redis.conf > /mnt/config/redis/redis.conf
              if [[ $ordinal -ne 0 ]]; then
                MASTER_IP=${REDIS_POD_NAME}-0.${REDIS_SERVICE_NAME}
                echo "slaveof $MASTER_IP $REDIS_MASTER_PORT" >> /mnt/config/redis/redis.conf
              else
                MASTER_IP=${SERVER_IP}
              fi
              cat>>/mnt/config/redis/redis.conf<<EOF
              port 6379
              requirepass $REDIS_PWD
              masterauth $REDIS_PWD
              logfile redis.log
              EOF
              cat>/mnt/config/sentinel/redis.conf<<EOF
              port 26379
              sentinel monitor $REDIS_MASTER_NAME $MASTER_IP $REDIS_MASTER_PORT $QUORUM
              sentinel down-after-milliseconds $REDIS_MASTER_NAME $DOWN_AFTER
              sentinel failover-timeout $REDIS_MASTER_NAME $FAILOVER_TIMEOUT
              sentinel parallel-syncs $REDIS_MASTER_NAME $PARALLEL_SYNCS
              sentinel auth-pass $REDIS_MASTER_NAME $REDIS_PWD
              EOF
          env:
            - name: REDIS_PWD
              valueFrom:
                secretKeyRef:
                  name: redis-secret
                  key: REDIS_PWD
            - name: REDIS_POD_NAME
              value: redis
            - name: REDIS_SERVICE_NAME
              value: jeecg-boot-redis
            - name: SERVER_IP
              valueFrom:
                fieldRef:
                  fieldPath: status.podIP
          envFrom:
            - configMapRef:
                name: redis-config
          volumeMounts:
            - name: redis-conf
              mountPath: /mnt/config/redis
            - name: sentinel-conf
              mountPath: /mnt/config/sentinel
            - name: config-map
              mountPath: /mnt/config-map
      containers:
        - name: redis
          image: redis:5.0.7
          imagePullPolicy: IfNotPresent
          command:
            - bash
            - "-c"
            - |
              exec redis-server /usr/local/etc/redis/redis.conf
          env:
            - name: REDIS_PWD
              valueFrom:
                secretKeyRef:
                  name: redis-secret
                  key: REDIS_PWD
          envFrom:
            - configMapRef:
                name: redis-config
          ports:
            - name: redis
              containerPort: 6379
          volumeMounts:
            - name: data
              mountPath: /data
              subPath: redis
            - name: redis-conf
              mountPath: /usr/local/etc/redis
          resources:
            requests:
              cpu: 500m
              memory: 512Mi
          livenessProbe:
            exec:
              command:
                - bash
                - "-c"
                - |
                  set -ex
                  redis-cli -p $REDIS_MASTER_PORT -a $REDIS_PWD ping
            initialDelaySeconds: 30
            periodSeconds: 5
            timeoutSeconds: 5
          readinessProbe:
            exec:
              # Check we can execute queries over TCP (skip-networking is off).
              command:
                - bash
                - "-c"
                - |
                  set -ex
                  redis-cli -p $REDIS_MASTER_PORT -a $REDIS_PWD ping
            initialDelaySeconds: 30
            periodSeconds: 10
            timeoutSeconds: 5
        - name: sentinel
          image: redis:5.0.7
          imagePullPolicy: IfNotPresent
          command:
            - bash
            - "-c"
            - |
              set -ex
              until redis-cli -p 6379 -a $REDIS_PWD info replication; do
              echo "Waiting for redis to be ready (accepting connections)"
              sleep 5
              done
              echo "Initializing replication from clone position"
              redis-server /usr/local/etc/redis/redis.conf --sentinel
          ports:
            - name: sentinel
              containerPort: 26379
          env:
            - name: REDIS_PWD
              valueFrom:
                secretKeyRef:
                  name: redis-secret
                  key: REDIS_PWD
          envFrom:
            - configMapRef:
                name: redis-config
          volumeMounts:
            - name: data
              mountPath: /data
              subPath: sentinel
            - name: sentinel-conf
              mountPath: /usr/local/etc/redis/
          resources:
            requests:
              cpu: 100m
              memory: 256Mi
          livenessProbe:
            exec:
              command:
                - bash
                - "-c"
                - |
                  set -ex
                  redis-cli -p 26379 -a $REDIS_PWD ping
            initialDelaySeconds: 30
            periodSeconds: 5
            timeoutSeconds: 5
          readinessProbe:
            exec:
              command:
                - bash
                - "-c"
                - |
                  set -ex
                  redis-cli -p 26379 -a $REDIS_PWD ping
            initialDelaySeconds: 30
            periodSeconds: 10
            timeoutSeconds: 5
      volumes:
        - name: redis-conf
          emptyDir: {}
        - name: sentinel-conf
          emptyDir: {}
        - name: config-map
          configMap:
            name: redis-config
  volumeClaimTemplates:
    - metadata:
        name: data
        namespace: jeecg-boot
      spec:
        accessModes:
        - ReadWriteMany
        storageClassName: "nfs-client"
        resources:
          requests:
            storage: 6Gi

RabbitMQ的集群部署

---
apiVersion: v1
kind: ConfigMap
metadata:
  name: rabbitmq-config
  namespace: jeecg-boot
  labels:
    addonmanager.kubernetes.io/mode: Reconcile
data:
    enabled_plugins: |
      [rabbitmq_management,rabbitmq_peer_discovery_k8s,rabbitmq_delayed_message_exchange].
    rabbitmq.conf: |
      default_user = admin
      default_pass = BCw3kkwHFVNj
      cluster_formation.peer_discovery_backend = rabbit_peer_discovery_k8s
      cluster_formation.k8s.host = kubernetes.default.svc.cluster.local
      cluster_formation.k8s.address_type = hostname
      cluster_formation.node_cleanup.interval = 30
      cluster_formation.node_cleanup.only_log_warning = true
      cluster_partition_handling = autoheal
      queue_master_locator=min-masters
      loopback_users.guest = false
      cluster_formation.randomized_startup_delay_range.min = 0
      cluster_formation.randomized_startup_delay_range.max = 2
      vm_memory_high_watermark.absolute = 2GB
      disk_free_limit.absolute = 4GB
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
---
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
rules:
- apiGroups: [""]
  resources: ["endpoints"]
  verbs: ["get"]
---
kind: RoleBinding
apiVersion: rbac.authorization.k8s.io/v1
metadata:
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: jeecg-boot-rabbitmq
subjects:
- kind: ServiceAccount
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
---
kind: Service
apiVersion: v1
metadata:
  labels:
    app: jeecg-boot-rabbitmq
    type: LoadBalancer
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
spec:
  clusterIP: None
  ports:
  - name: amqp
    port: 5672
    protocol: TCP
    targetPort: 5672
  selector:
    app: jeecg-boot-rabbitmq
---
kind: Service
apiVersion: v1
metadata:
  labels:
    app: jeecg-boot-rabbitmq
  name: rabbitmq-cluster-manage
  namespace: jeecg-boot
spec:
  ports:
  - name: http
    port: 15672
    protocol: TCP
    targetPort: 15672
    nodePort: 30672
  selector:
    app: jeecg-boot-rabbitmq
  type: NodePort      
---
kind: StatefulSet
apiVersion: apps/v1
metadata:
  labels:
    app: jeecg-boot-rabbitmq
  name: jeecg-boot-rabbitmq
  namespace: jeecg-boot
spec:
  replicas: 3
  selector:
    matchLabels:
      app: jeecg-boot-rabbitmq
  serviceName: jeecg-boot-rabbitmq
  template:
    metadata:
      namespace: jeecg-boot
      labels:
        app: jeecg-boot-rabbitmq
    spec:
      serviceAccountName: jeecg-boot-rabbitmq
      terminationGracePeriodSeconds: 30
      containers:
      - name: jeecg-boot-rabbitmq
        image: rabbitmq:3.8.3-management
        imagePullPolicy: IfNotPresent
        args:
        - -c
        - cp -v /etc/rabbitmq/rabbitmq.conf ${RABBITMQ_CONFIG_FILE}; exec docker-entrypoint.sh
          rabbitmq-server
        command:
        - sh
        env:
        - name: TZ
          value: 'Asia/Shanghai'
        - name: POD_IP
          valueFrom:
            fieldRef:
              fieldPath: status.podIP
        - name: POD_NAME
          valueFrom:
            fieldRef:
              fieldPath: metadata.name
        - name: POD_NAMESPACE
          valueFrom:
            fieldRef:
              fieldPath: metadata.namespace
        - name: RABBITMQ_USE_LONGNAME
          value: "true"
        - name: RABBITMQ_ERLANG_COOKIE
          value: 'SWvCP0Hrqv43NG7GybHC95ntCJKoW8UyNFWnBEWG8TY='
        - name: K8S_SERVICE_NAME
          value: jeecg-boot-rabbitmq
        - name: RABBITMQ_NODENAME
          value: rabbit@$(POD_NAME).$(K8S_SERVICE_NAME).$(POD_NAMESPACE).svc.cluster.local
        - name: K8S_HOSTNAME_SUFFIX
          value: .$(K8S_SERVICE_NAME).$(POD_NAMESPACE).svc.cluster.local
        - name: RABBITMQ_CONFIG_FILE
          value: /var/lib/rabbitmq/rabbitmq.conf
        livenessProbe:
          exec:
            command:
            - rabbitmq-diagnostics
            - status
          # See https://www.rabbitmq.com/monitoring.html for monitoring frequency recommendations.
          initialDelaySeconds: 60
          periodSeconds: 60
          timeoutSeconds: 15
        ports:
        - name: http
          containerPort: 15672
          protocol: TCP
        - name: amqp
          containerPort: 5672
          protocol: TCP
        readinessProbe:
          exec:
            command:
            - rabbitmq-diagnostics
            - status
          initialDelaySeconds: 20
          periodSeconds: 60
          timeoutSeconds: 10
        volumeMounts:
        - mountPath: /etc/rabbitmq
          name: config-volume
          readOnly: false
        - mountPath: /var/lib/rabbitmq
          name: rabbitmq-storage
          readOnly: false
        - name: timezone
          mountPath: /etc/localtime
          readOnly: true
      volumes:
      - name: config-volume
        configMap:
          name: rabbitmq-config
          items:
          - key: rabbitmq.conf
            path: rabbitmq.conf
          - key: enabled_plugins
            path: enabled_plugins
      - name: timezone
        hostPath:
          path: /usr/share/zoneinfo/Asia/Shanghai
  volumeClaimTemplates:
  - metadata:
      name: rabbitmq-storage
      namespace: jeecg-boot
    spec:
      accessModes:
      - ReadWriteMany
      storageClassName: "nfs-client"
      resources:
        requests:
          storage: 6Gi

GateWay网关的资源清单

apiVersion: apps/v1
kind: Deployment
metadata:
  name: jeecg-boot-gateway
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-gateway
spec:
  replicas: 3
  selector:
    matchLabels:
      app: jeecg-boot-gateway
  template:
    metadata:
      labels:
        app: jeecg-boot-gateway
    spec:
      containers:
      - name: jeecg-boot-gateway
        image: 192.168.0.7:50080/repository/jeecg-boot-gateway:v1.0.0
        imagePullPolicy: Always
        ports:
        - containerPort: 9999
        env:
        - name: NACOS-PASS
          valueFrom:
            configMapKeyRef:
              name: nacos-cm
              key: nacos.password
      imagePullSecrets:
      - name: harbor     
---
apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-gateway
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-gateway
spec:
  selector:
    app: jeecg-boot-gateway
  ports:
  - name: http
    port: 9999
    protocol: TCP
    targetPort: 9999
    nodePort: 30099
  type: NodePort

System模块资源清单文件

apiVersion: apps/v1
kind: Deployment
metadata:
  name: jeecg-boot-system
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-system
spec:
  replicas: 3
  selector:
    matchLabels:
      app: jeecg-boot-system
  template:
    metadata:
      labels:
        app: jeecg-boot-system
    spec:
      containers:
      - name: jeecg-boot-system
        image: 192.168.0.7:50080/repository/jeecg-boot-system:v1.0.0
        imagePullPolicy: Always
        ports:
        - containerPort: 7001
        env:
        - name: NACOS-PASS
          valueFrom:
            configMapKeyRef:
              name: nacos-cm
              key: nacos.password
      imagePullSecrets:
      - name: harbor  
---
apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-system
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-system
spec:
  selector:
    app: jeecg-boot-system
  ports:
  - name: http
    port: 7001
    targetPort: 7001
  type: ClusterIP

其他微服务资源清单示例（数据清洗服务）

apiVersion: apps/v1
kind: Deployment
metadata:
  name: jeecg-boot-ind
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-ind
spec:
  replicas: 3
  selector:
    matchLabels:
      app: jeecg-boot-ind
  template:
    metadata:
      labels:
        app: jeecg-boot-ind
    spec:
      imagePullSecrets:
      - name: harbor
      volumes:
      - name: temp
        hostPath:
          path: /opt/temp
      - name: workspace
        hostPath:
          path: /opt/workspace
      - name: up-files
        hostPath:
          path: /opt/upFiles
      containers:
      - name: jeecg-boot-ind
        image: 192.168.0.7:50080/repository/jeecg-boot-ind:v1.0.0
        imagePullPolicy: Always
        ports:
        - containerPort: 7003
        volumeMounts:
        - name: temp
          mountPath: /opt/temp
        - name: workspace
          mountPath: /opt/workspace
        - name: up-files
          mountPath: /opt/upFiles
        env:
        - name: NACOS-PASS
          valueFrom:
            configMapKeyRef:
              name: nacos-cm
              key: nacos.password
---
apiVersion: v1
kind: Service
metadata:
  name: jeecg-boot-ind
  namespace: jeecg-boot
  labels:
    app: jeecg-boot-ind
spec:
  selector:
    app: jeecg-boot-ind
  ports:
  - name: http
    port: 7003
    targetPort: 7003
  type: ClusterIP
William_Franca
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
K8S监控主机资源node-exporter镜像及资源清单文件
12-22
原文链接：https://blog.csdn.net/m0_37814112/article/details/122041607 说明：Kubernetes监控主机资源node-exporter镜像及资源清单文件
微服务综合部署——SpringBoot项目制作Docker镜像注册在Zookeeper并利用K8S技术部署
lqm1094583745的博客
12-18 769
微服务综合部署——SpringBoot项目制作Docker镜像注册在Zookeeper并利用K8S技术部署
docker下搭建全套微服务环境指导说明文档和部署命令
binggoling
05-21 629
这里写目录标题docker下搭建全套微服务环境指导说明文档和部署命令总的架构图1.服务器准备2.centos安装docker环境3.docker集群swarm配置(这一步看自己需要执行)4.docker安装mysql8.05.redis部署6.rocketMQ部署7.nacos集群部署8.keepalive+nginx高可用部署9.springcloud应用微服务9.1 [springcloud微服务之注册发现和配置中心Nacos使用](https://blog.csdn.net/qq_30442207/a
springcloud：微服务涉及哪些技术、有哪些核心组件（二）
55555的博客
04-02 8278
0. 引言 上一期我们介绍了什么是微服务，微服务的基础概念，那么本期我们来介绍一下微服务涉及的技术点以及所需要的组件 1. 微服务涉及哪些技术 1.1、基础技术 首先每个微服务都可以看作是单机架构，所以最基础的就要要求你掌握单机架构的知识，单机架构最少量要求掌握的知识包括： java mysql springboot mybatis,mybatis-plus linux 如果你对于以上知识还没有掌握，那么可以参考我之前的学习路线文章： 初级java学习路线 1.2、部分中间件 redis MQ（Roc
分布式 微服务
qq_41358574的博客
03-09 1494
微服务整理的知识
jeecg-boot微服务部署步骤详细说明
qq_40015409的博客
09-15 3974
通常小企业是如何成长起来的？接外包，然后将公司慢慢的养起来，最后开始研发自己的产品，产品上线，上市！哈哈，可能有点理想化了，但是身边好多朋友都自己出去创业了，今儿个张三开了个公司，明儿个李四也注册了个公司，但是了解了下，大家刚开始都是靠外包起步，有资源的利用资源，没有资源的找资源。那么问题来了，作为一个外包公司，最重要的干活的效率，将时间就是金钱提现的淋漓尽致。所以在写项目的时候，定是怎么方便怎么来，能ctrl+c,v的绝对不会自己写。
Spring Cloud Alibaba全家桶（六）——微服务组件Sentinel介绍与使用
小新要变强的博客
03-10 3722
本文小新为大家带来 微服务组件Sentinel介绍与使用相关知识，具体内容包括分布式系统存在的问题，分布式系统问题的解决方案，Sentinel介绍，Sentinel快速开始（包括：API实现Sentinel资源保护，@SentinelResource注解实现资源保护），Sentinel控制台，Spring Cloud Alibaba整合Sentinel等进行详尽介绍~
K8S配合 jenkins 完整一键安装
weixin_52474889的博客
07-14 437
---------------------------------------------初始化创建容器-------------------------------------------------------------文件中所有的 test 都要换成你创建容器时的名字 demo换成你的 jar 包名字 command中的目录要和打包时候一致。流程为：代码打包--打成 docker 镜像--上传到阿里云镜像管理--通过阿里云镜像内容更新现有容器。创建容器 demo 为取好的名字，记住后面要用。
自动化部署实践 （Jenkins+Git+Docker+阿里云k8s）
Step_By_XXX的博客
01-29 5796
基于Jenkins+Git+Docker+阿里云k8s，对项目进行自动化部署的实践过程记录，主要说明了Jenkins的流水线脚本以其他一些相关的配置
k8s NFS挂载出现 mount.nfs: access denied by server while mounting 192.168.153.128:/nfs/data
qq_15138049的博客
11-17 944
### pod 一直处于pending状态 root@ubuntu:/opt/module/k8s# kubectl get pods -n nfs-client NAME READY STATUS RESTARTS AGE nfs-client-provisioner-6956c9b6f8-cwl8j 0/1 Pending 0 33m root@ubuntu:/opt/m
K8S主机Prometheus监控kube-state-metrics资源清单及镜像文件
12-30
原文链接：https://blog.csdn.net/m0_37814112/article/details/122170537 说明：上述资源包括部署清单文件、镜像文件、告警规则文件
K8S监控blackbox-exporter镜像及资源清单文件
01-18
原文链接：https://blog.csdn.net/m0_37814112/article/details/122503583
K8S部署metrics-server-v0.6.0资源清单及镜像文件
01-24
原文链接：https://blog.csdn.net/m0_37814112/article/details/122666995 说明： 1、支持支持的Kubernetes版本1.19+ 2、包含yaml文件和镜像，直接apply即可部署完成
K8S资源对象监控kube-state-metrics-2.0.0镜像及资源清单文件
12-22
原文链接：https://blog.csdn.net/m0_37814112/article/details/122041607 说明：K8S资源对象监控kube-state-metrics-2.0.0镜像文件及资源清单文件
微服务下必须了解的4种部署策略！
码猿技术专栏
06-15 170
大家好，我是不才陈某~在项目迭代的过程中，不可避免需要上线。上线对应着部署，或者重新部署；部署对应着修改；修改则意味着风险。目前有很多部署发布的技术， 这儿将常见的做一个总结。上面所说难免有些抽象， 举一个情景例子， 假如你是微博项目负责人员， 现在新版本较原来的老版本有很大的改变， 这设计到服务架构、前端UI等等， 经过测试功能没有障碍， 那么这时候如何让用户切换到新的版本呢?显而易见， 第一次...
将Petclinic微服务部署到本地K8s环境
Kason_iWiki
11-18 411
文章目录1.将Petclinic重构为微服务架构2.本地K8s部署架构3.准备资源配置清单3.1 customer服务3.2 visits服务3.3 vets服务3.4 web-app应用3.5 gateway应用4.应用资源配置清单5. 浏览器校验 1.将Petclinic重构为微服务架构 项目源码:https://github.com/chengyinwu-hash/spring-petclinic-msa 微服务架构需要引入网关或者反向代理，实现反向路由和转发 Web App实现API聚合+单页SP
在Kubernetes(k8s)上部署整个SpringCloud微服务应用
最新发布
XiaoHH的博客
10-19 4857
Kubernetes上部署整个SpringCloud微服务应用，并使用ingress暴露应用。部署包括nacos、redis、mysql等组件。同时还部署monitor监控模块。
微服务项目丨基于Kubernetes集群PaaS云平台 Kubesphere部署
weixin_47758895的博客
05-06 571
在安装之前，需要配置kubernetes个课程上的默认存储类型。
JEECG微服务架构配置和运行
技术+管理+经验+沟通+人品=>合格的项目管理者
05-17 4068
Jeecg最新版本微服务架构的配合和启动，初次接触，还是有一些复杂的。本文基于官网介绍进行的配置。列举了一些注意点，帮助新手避免踩坑。 JEECG的微服务架构粗看很复杂，其实不看没关系，jeecg已经帮我们架构好了，会用就行。一般情况下做政府、行业的定制化系统，应该不会存在大并发和大数据查询效率问题。有个10万用户集中2天单点活跃2000，单点写并发1w+的系统准备用如下架构，届时出性能分析报告和进一步的架构说明。
k8s部署zabbix-server详细步骤与yaml文件
05-25
以下是Kubernetes部署Zabbix Server的详细步骤和YAML文件： 1. 创建PV和PVC 在Kubernetes上部署Zabbix Server，需要使用持久卷（PV）和持久卷声明（PVC）来存储数据。下面是一个示例PVC YAML文件： ``` apiVersion: v1 kind: PersistentVolumeClaim metadata: name: zabbix-db-pvc spec: accessModes: - ReadWriteOnce resources: requests: storage: 10Gi ``` 使用kubectl命令创建PVC： ``` kubectl apply -f zabbix-db-pvc.yaml ``` 2. 创建ConfigMap Zabbix Server需要使用一些配置文件，可以将这些文件打包为一个ConfigMap。下面是一个示例ConfigMap YAML文件： ``` apiVersion: v1 kind: ConfigMap metadata: name: zabbix-server-config data: zabbix_server.conf: | DBHost=zabbix-db DBName=zabbix DBUser=zabbix DBPassword=zabbix AlertScriptsPath=/usr/lib/zabbix/alertscripts ExternalScripts=/usr/lib/zabbix/externalscripts ``` 使用kubectl命令创建ConfigMap： ``` kubectl apply -f zabbix-server-configmap.yaml ``` 3. 创建Deployment和Service 下面是一个示例Deployment YAML文件： ``` apiVersion: apps/v1 kind: Deployment metadata: name: zabbix-server spec: replicas: 1 selector: matchLabels: app: zabbix-server template: metadata: labels: app: zabbix-server spec: containers: - name: zabbix-server image: zabbix/zabbix-server-mysql:latest volumeMounts: - name: zabbix-db-data mountPath: /var/lib/mysql - name: zabbix-server-config mountPath: /etc/zabbix/zabbix_server.conf subPath: zabbix_server.conf env: - name: MYSQL_DATABASE value: zabbix - name: MYSQL_USER value: zabbix - name: MYSQL_PASSWORD value: zabbix - name: MYSQL_HOST value: zabbix-db - name: MYSQL_PORT value: "3306" ports: - containerPort: 10051 volumes: - name: zabbix-db-data persistentVolumeClaim: claimName: zabbix-db-pvc - name: zabbix-server-config configMap: name: zabbix-server-config ``` 使用kubectl命令创建Deployment： ``` kubectl apply -f zabbix-server-deployment.yaml ``` 下面是一个示例Service YAML文件： ``` apiVersion: v1 kind: Service metadata: name: zabbix-server spec: selector: app: zabbix-server ports: - name: zabbix port: 10051 protocol: TCP targetPort: 10051 ``` 使用kubectl命令创建Service： ``` kubectl apply -f zabbix-server-service.yaml ``` 这样，Zabbix Server就成功部署到了Kubernetes上。可以使用kubectl命令查看Deployment和Service状态： ``` kubectl get deployments kubectl get services ``` 如果一切正常，应该能够看到Zabbix Server的Deployment和Service都处于“运行中”状态。

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值