k8s ConfigMap 配置中心

• k8s ConfigMap 配置中心
  • ConfigMap 简介
  • ConfigMap的yaml定义
    • 示例
  • 通过ConfigMap达到配置中心的作用
    • 主要流程
    • 查看当前pod上的目录信息
    • 控制application.json的配置
    • 修改并再次发布
    • 再次发布

ConfigMap 简介

ConfigMap用于保存配置数据的键值对，可以用来保存单个属性，也可以用来保存配置文件。ConfigMap跟secret很类似，但它可以更方便地处理不包含敏感信息的字符串。

注意

• ConfigMap必须在Pod引用它之前创建
• 使用envFrom时，将会自动忽略无效的键
• Pod只能使用同一个命名空间内的ConfigMap

ConfigMap的yaml定义

示例

apiVersion: v1
kind: ConfigMap
metadata:
  name: appsettings.name-api
  namespace: netcore
data:
  appsettings.json: |
   {
    "Logging": {
      "LogLevel": {
        "Default": "Information",
        "Microsoft": "Warning",
        "Microsoft.Hosting.Lifetime": "Information"
      }
    },
    "AllowedHosts": "*"
   }

相信大伙都看得出来这是一个ConfigMap关于appsetting.json的配置

通过ConfigMap达到配置中心的作用

主要流程

查看当前pod上的目录信息

控制application.json的配置

修改yaml文件

1. 添加上述的yaml放到最前面
2. 添加volme

        volumes:
        - name: appsettings
          ConfigMap:
            name: appsettings.name-api

3. 添加volumeMounts

          volumeMounts:
          - name: appsettings
            mountPath: /app/appsettings.json
            subPath: appsettings.json

完整的yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: appsettings.name-api
  namespace: netcore
data:
  appsettings.json: |
   {
    "Logging": {
      "LogLevel": {
        "Default": "Information",
        "Microsoft": "Warning",
        "Microsoft.Hosting.Lifetime": "Information"
      }
    },
    "AllowedHosts": "*"
   }
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: name-api
  namespace: netcore
  labels:
    name: name-api
spec:
  replicas: 3
  selector:
    matchLabels:
      name: name-api
  template:
      metadata:
        labels:
          name: name-api
      spec:
        containers:
        - name: name-api
          env:
          - name: HOSTNAME_COMMAND
            valueFrom:
              fieldRef: 
                fieldPath: metadata.name
          volumeMounts:
          - name: appsettings
            mountPath: /app/appsettings.json
            subPath: appsettings.json
          image: ccr.ccs.tencentyun.com/hbtest/name-api:v2
          ports:
          - containerPort: 80
          imagePullPolicy: Always
        imagePullSecrets:
          - name: tenxunyunregistrykey
        volumes:
        - name: appsettings
          configMap:
            name: appsettings.name-api
---
kind: Service
apiVersion: v1
metadata:
  name: name-api
  namespace: netcore
spec:
  type: NodePort
  ports:
    - port: 80
      targetPort: 80
  selector:
    name: name-api

查看结果

修改并再次发布

修改 Infomaction 为 Trace

apiVersion: v1
kind: ConfigMap
metadata:
  name: appsettings.name-api
  namespace: netcore
data:
  appsettings.json: |
   {
    "Logging": {
      "LogLevel": {
        "Default": "Trace",
        "Microsoft": "Warning",
        "Microsoft.Hosting.Lifetime": "Information"
      }
    },
    "AllowedHosts": "*"
   }
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: name-api
  namespace: netcore
  labels:
    name: name-api
spec:
  replicas: 3
  selector:
    matchLabels:
      name: name-api
  template:
      metadata:
        labels:
          name: name-api
      spec:
        containers:
        - name: name-api
          env:
          - name: HOSTNAME_COMMAND
            valueFrom:
              fieldRef: 
                fieldPath: metadata.name
          volumeMounts:
          - name: appsettings
            mountPath: /app/appsettings.json
            subPath: appsettings.json
          image: ccr.ccs.tencentyun.com/hbtest/name-api:v2
          ports:
          - containerPort: 80
          imagePullPolicy: Always
        imagePullSecrets:
          - name: tenxunyunregistrykey
        volumes:
        - name: appsettings
          configMap:
            name: appsettings.name-api
---
kind: Service
apiVersion: v1
metadata:
  name: name-api
  namespace: netcore
spec:
  type: NodePort
  ports:
    - port: 80
      targetPort: 80
  selector:
    name: name-api

再次发布

查看相关pod
我们会发现它并没有改变。

删除副本集并再次查看结果