apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: example-service
  name: example-service
spec:
  #副本數(shù)量
  replicas: {{.pod_replicas}}
  selector:
    matchLabels:
      app: example-service
  minReadySeconds: 30 #設(shè)置升級(jí)延遲時(shí)間15秒,等待15秒后升級(jí)
  strategy:
    type: RollingUpdate
    rollingUpdate:
      maxSurge: 1   #升級(jí)過程中最多可以比原先設(shè)置多出的POD數(shù)量
      maxUnavailable: 0
  template:
    metadata:
      labels:
        app: example-service
        monitortype: backend
    spec:
      #以下內(nèi)容為可選,容器調(diào)度策略，保證同一deployment的多個(gè)副本位于不同的機(jī)器上，防止單節(jié)點(diǎn)掛掉導(dǎo)致服務(wù)不可用,由于涉及到要與運(yùn)維溝通資源情況,無法直接給予固定配置。
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
            - labelSelector:
                matchExpressions:
                  - key: app
                    operator: In
                    values:
                      - example-service
              topologyKey: kubernetes.io/hostname
      containers:
        - image: example-service:latest
          imagePullPolicy: IfNotPresent
          name: example-service
          lifecycle:
            preStop:
              exec:
                command:
                  - curl
                  - '-XPOST'
                  - '127.0.0.1:8080/actuator/shutdown'      
          readinessProbe:                # 就緒探針
            httpGet:
              path: /actuator/health/readiness
              port: 8080
            initialDelaySeconds: 30      # 延遲加載時(shí)間
            periodSeconds: 10            # 重試時(shí)間間隔
            timeoutSeconds: 1            # 超時(shí)時(shí)間設(shè)置
            successThreshold: 1          # 健康閾值
            failureThreshold: 3          # 不健康閾值
          livenessProbe:                 # 存活探針
            httpGet:
              path: /actuator/health/liveness
              port: 8080
            initialDelaySeconds: 30      # 延遲加載時(shí)間
            periodSeconds: 10            # 重試時(shí)間間隔
            timeoutSeconds: 1            # 超時(shí)時(shí)間設(shè)置
            successThreshold: 1          # 健康閾值
            failureThreshold: 3          # 不健康閾值
          ports:
            - containerPort: 8080
              name: backend
              protocol: TCP
          envFrom:
            - configMapRef:
                #存放公共環(huán)境變量，比如：數(shù)據(jù)庫，redis，nacos等連接信息，每個(gè)項(xiàng)目的各個(gè)微服務(wù)基本都是一樣的。
                name: pub-cm
            - configMapRef:
                #存放個(gè)性化配置，對(duì)于個(gè)別的服務(wù)，除了公共變量外，會(huì)涉及其他引用信息。
                name: example-service-cm
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  apiVersion: v1
                  fieldPath: metadata.name
          resources:
            #設(shè)定以下是設(shè)定服務(wù)資源根據(jù)你的項(xiàng)目實(shí)際情況來
            limits: # limits是代表的資源上限,服務(wù)能消耗的資源上限
              cpu: {{.pod_cpu_limit}} #{limits_cpu}(必須),目前默認(rèn)單位為m,如果申請(qǐng)一核則為1024m,以此類推,默認(rèn)則為500m
              memory: {{.pod_memory_limit}} #{limits_mem}(必須),目前默認(rèn)單位為Mi,如果申請(qǐng)1G內(nèi)存則為1024Mi,以此類推,默認(rèn)則為2048Mi
            requests: # requests是服務(wù)所需最小的啟動(dòng)資源,設(shè)置后如果node達(dá)不到這個(gè)資源要求就會(huì)部署失敗
              cpu: {{.pod_cpu_request}} #{requests_cpu}(必須),目前默認(rèn)單位為m,如果申請(qǐng)一核則為1024m,以此類推,默認(rèn)則為250m
              memory: {{.pod_memory_request}} #{requests_mem}(必須),目前默認(rèn)單位為Mi,如果申請(qǐng)1G內(nèi)存則為1024Mi,以此類推,默認(rèn)則為500Mi
          # 以下為必須選項(xiàng),項(xiàng)目做日志采集
          volumeMounts:
            - name: host-time
              readOnly: true
              mountPath: /etc/localtime
            - name: example-service-log
              mountPath: /home/logs # 如果接入日志必須存在容器內(nèi)/home/logs文件夾下存放日志文件
              subPathExpr: $(POD_NAME)
      volumes:
        - name: example-service-log
          hostPath:
            path: /home/logs
            type: DirectoryOrCreate
        - name: host-time
          hostPath:
            path: /etc/localtime
            type: ''
      imagePullSecrets: # 寫死,前提是要執(zhí)行這個(gè)憑證創(chuàng)建命令
        - name: harborha-secret001fe
---
apiVersion: policy/v1beta1
kind: PodDisruptionBudget #設(shè)置pod最小可用數(shù)量
metadata:
  name: example-service-pdb
spec:
  minAvailable: 50%
  selector:
    matchLabels:
      app: example-service

@WebEndpoint(id = "deregister")
@Slf4j
@ConditionalOnClass(value = WebEndpoint.class)
public class NacosServiceDeregisterEndpoint {
    private final NacosDiscoveryProperties nacosDiscoveryProperties;
    private final NacosRegistration nacosRegistration;
    private final NacosServiceRegistry nacosServiceRegistry;
    public NacosServiceDeregisterEndpoint(NacosDiscoveryProperties nacosDiscoveryProperties, NacosRegistration nacosRegistration, NacosServiceRegistry nacosServiceRegistry) {
        this.nacosDiscoveryProperties = nacosDiscoveryProperties;
        this.nacosRegistration = nacosRegistration;
        this.nacosServiceRegistry = nacosServiceRegistry;
    }
    @ReadOperation
    public String deregisterEndPoint() {
        String serviceName = nacosDiscoveryProperties.getService();
        String groupName = nacosDiscoveryProperties.getGroup();
        String clusterName = nacosDiscoveryProperties.getClusterName();
        String ip = nacosDiscoveryProperties.getIp();
        int port = nacosDiscoveryProperties.getPort();
        log.info("Deregister from the Nacos, ServiceName:{}, GroupName:{}, ClusterName:{}, IP:{}, Port:{}", serviceName, groupName, clusterName, ip, port);
        // 設(shè)置服務(wù)下線
        nacosServiceRegistry.setStatus(nacosRegistration, "DOWN");
        return "success";
    }
}

management:
  endpoint:
    health:
      show-details: always
      probes:
        enabled: true
    metrics:
      enabled: true
    shutdown:
      enabled: true
  endpoints:
    web:
      exposure:
        include: "health,shutdown,metrics,deregister"
  server:
    port: 8080
  metrics:
    tags:
      application: ${spring.application.name}