Kubernetes域名解析问题排查

最新推荐文章于 2024-09-04 16:55:13 发布

帜歩

最新推荐文章于 2024-09-04 16:55:13 发布

阅读量2k

点赞数

文章标签： kubernetes

本文链接：https://blog.csdn.net/l862250423/article/details/126976887

版权

本文主要探讨Kubernetes中CoreDNS作为默认DNS服务器的角色，如何查看和配置CoreDNS，以及如何排查和解决域名解析异常的问题。内容包括检查coredns-deployment的yaml文件，确保Pod使用CoreDNS服务，排查宿主机的DNS解析，并调整CoreDNS的forward策略以应对偶尔的域名解析失败。

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

从Kubernetes 1.12开始，CoreDNS就成了Kubernetes的默认DNS服务器

coredns

下面为一份coredns-deployment的yaml文件

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    k8s-app: kube-dns
  name: coredns
  namespace: kube-system
spec:
  progressDeadlineSeconds: 600
  replicas: 2
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kube-dns
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 1
    type: RollingUpdate
  template:
    metadata:
      creationTimestamp: null
      labels:
        k8s-app: kube-dns
    spec:
      containers:
      - args:
        - -conf
        - /etc/coredns/Corefile
        image: k8s.gcr.io/coredns/coredns:v1.8.4
        imagePullPolicy: IfNotPresent
        livenessProbe:
          failureThreshold: 5
          httpGet:
            path: /health
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 60
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 5
        name: coredns
        ports:
        - containerPort: 53
          name: dns
          protocol: UDP
        - containerPort: 53
          name: dns-tcp
          protocol: TCP
        - containerPort: 9153
          name: metrics
          protocol: TCP
        readinessProbe:
          failureThreshold: 3
          httpGet:
            path: /ready
            port: 8181
            scheme: HTTP
          periodSeconds: 10
          successThreshold: 1
          timeoutSeconds: 1
        resources:
          limits:
            memory: 170Mi
          requests:
            cpu: 100m
            memory: 70Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            add:
            - NET_BIND_SERVICE