k8s-部署-17-coreDNS详解
k8s-部署-17-coreDNS详解
1、coreDNS的用途:
下载地址:kubernetes/coredns.yaml.base at master · kubernetes/kubernetes · GitHub
coreDNS在k8s 中的主要用途是:是用作服务发现,也就是服务(或者叫应用)之间相互定位的过程
2、为什么需要服务发现呢?
2.1、这就要先说说在k8s当中Pod的特点:
- 服务的动态性强:容器在k8s中迁移,会导致Pod的IP地址产生变化
- 更新发布很频繁:版本迭代很快,并且IP地址会变化
- 服务支持自动伸缩:服务伸缩时会使Pod的IP地址出现增加或者减少
2.2、Service
- service 资源就是解决Pod服务发现问题,用service资源来代理后端的pod,通过暴露service资源的固定IP地址(也是cluster IP),来解决上面所述的pod 多变不固定的问题
- 抽象出了Service资源,通过标签选择器,关联一组pod
- 抽象出了集群网络,通过相对固定的“集群IP”,使服务接入点固定
2.3、service资源提供了一个不变的集群IP供外部访问,但
- IP地址毕竟难以记忆
- service资源可能也会被销毁和创建
- 能不能将service资源名称和service暴露的集群网络IP对应
- 类似域名与IP关系,则只需记服务名就能自动匹配服务IP
- 岂不就达到了service服务的自动发现
2.4、K8S里服务发现的方式 - DNS
实现K8S里DNS功能的插件:
- kube-dns:kuberbetes-v1.2至kuberbetes-v1.10
- Coredns:kuberbetes-v1.11至今
备注:K8S里的DNS不是万能的!它应该只负责自动维护“服务名” -> “集群网络IP”之间的关系
3、部署CoreDNS
3.1、部署K8S的内网资源配置清单http服务
在运维主机上,配置一个nginx虚拟主机,用以提供K8S统一的资源配置清单访问入口
~]# mkdir /data/k8s-yaml ~]# cat /etc/nginx/conf.d/k8s-yaml.od.com.conf server { listen 80; server_name k8s-yaml.od.com; location / { autoindex on; default_type text/plain; root /data/k8s-yaml; } } ~]# nginx -t ~]# nginx -s reload
3.2、配置内网DNS解析
~]# vi /var/named/od.com.zone $ORIGIN od.com. $TTL 600 ; 10 minutes @ IN SOA dns.od.com. dnsadmin.od.com. ( 2019120903 ; serial # 03,序列号做下前滚 10800 ; refresh (3 hours) 900 ; retry (15 minutes) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) NS dns.od.com. $TTL 60 ; 1 minute dns A 10.4.7.11 harbor A 10.4.7.200 k8s-yaml A 10.4.7.200 ~]# systemctl restart named ~]# dig -t A k8s-yaml.od.com @10.4.7.11 +short ~]# cd /data/k8s-yaml/ ]# mkdir coredns
3.3、制作镜像
在运维主机上制作相应的镜像
]# docker pull coredns/coredns:1.6.5 ]# docker tag coredns/coredns:1.6.5 harbor.od.com/public/coredns:v1.6.5 ]# docker push harbor.od.com/public/coredns:v1.6.5
3.4、创建资源管理配置清单
1 | mkdir -p /data/k8s-yaml/coredns |
rbac集群权限清单:
[root@hdss7-200 coredns]# cat rbac.yaml apiVersion: v1 kind: ServiceAccount metadata: name: coredns namespace: kube-system labels: kubernetes.io/cluster-service: "true" addonmanager.kubernetes.io/mode: Reconcile --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: labels: kubernetes.io/bootstrapping: rbac-defaults addonmanager.kubernetes.io/mode: Reconcile name: system:coredns rules: - apiGroups: - "" resources: - endpoints - services - pods - namespaces verbs: - list - watch --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: annotations: rbac.authorization.kubernetes.io/autoupdate: "true" labels: kubernetes.io/bootstrapping: rbac-defaults addonmanager.kubernetes.io/mode: EnsureExists name: system:coredns roleRef: apiGroup: rbac.authorization.k8s.io kind: ClusterRole name: system:coredns subjects: - kind: ServiceAccount name: coredns namespace: kube-system
configmap配置清单:
[root@hdss7-200 coredns]# cat cm.yaml apiVersion: v1 kind: ConfigMap metadata: name: coredns namespace: kube-system data: Corefile: | .:53 { errors log health ready kubernetes cluster.local 192.168.0.0/16 forward . 10.4.7.11 cache 30 loop reload loadbalance }
depoly控制器清单:
[root@hdss7-200 coredns]# cat dp.yaml apiVersion: apps/v1 kind: Deployment metadata: name: coredns namespace: kube-system labels: k8s-app: coredns kubernetes.io/name: "CoreDNS" spec: replicas: 1 selector: matchLabels: k8s-app: coredns template: metadata: labels: k8s-app: coredns spec: priorityClassName: system-cluster-critical serviceAccountName: coredns containers: - name: coredns image: harbor.od.com/public/coredns:v1.6.1 args: - -conf - /etc/coredns/Corefile volumeMounts: - name: config-volume mountPath: /etc/coredns ports: - containerPort: 53 name: dns protocol: UDP - containerPort: 53 name: dns-tcp protocol: TCP - containerPort: 9153 name: metrics protocol: TCP livenessProbe: httpGet: path: /health port: 8080 scheme: HTTP initialDelaySeconds: 60 timeoutSeconds: 5 successThreshold: 1 failureThreshold: 5 dnsPolicy: Default volumes: - name: config-volume configMap: name: coredns items: - key: Corefile path: Corefile
service资源清单:
[root@hdss7-200 coredns]# cat svc.yaml apiVersion: v1 kind: Service metadata: name: coredns namespace: kube-system labels: k8s-app: coredns kubernetes.io/cluster-service: "true" kubernetes.io/name: "CoreDNS" spec: selector: k8s-app: coredns clusterIP: 192.168.0.2 ports: - name: dns port: 53 protocol: UDP - name: dns-tcp port: 53 - name: metrics port: 9153 protocol: TCP
备注:官方coredns资源配置清单下载地址:
https://github.com/kubernetes/kubernetes/blob/master/cluster/addons/dns/coredns/coredns.yaml.base
3.5、应用资源配置清单
# 应用资源配置清单 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/rbac.yaml ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/cm.yaml ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/dp.yaml ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/svc.yaml # 查看创建的资源 ~]# kubectl get svc -n kube-system ~]# kubectl get all -n kube-system # 验证DNS
~]# dig -t A www.baidu.com @192.168.0.2 +short ~]# dig -t A hdss7-11.host.com @192.168.0.2 +short # 创建相应的服务来验证 ~]# kubectl create deployment nginx-dp --image=harbor.od.com/public/nginx:v1.7.9 -n kube-public ~]# kubectl expose deployment nginx-dp --port=80 -n kube-public ~]# dig -t A nginx-dp.kube-public.svc.cluster.local. @192.168.0.2 +short
3.6、CoreDNS:Kubernetes内部域名解析原理、弊端及优化方式:
http://ccnuo.com/
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· DeepSeek 开源周回顾「GitHub 热点速览」
· 记一次.NET内存居高不下排查解决与启示
· 物流快递公司核心技术能力-地址解析分单基础技术分享
· .NET 10首个预览版发布:重大改进与新特性概览!
· .NET10 - 预览版1新功能体验(一)