CoreDNS解决了什么问题?
k8s平台中,各种应用会随机分发到节点服务器上运行,外界无法找到应用的访问地址。
一、配置pod资源定义模板
(本次实验采用网络存储方式来保存pod定义模板,实际应用的时候也可以以本地文件的形式保存)
1.1 配置Nginx (在 k8s-5-141 主机上操作)
#添加nginx转发服务
[root@k8s-5-141 /]# vim /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;
}
}
# 创建需要用到的目录
[root@k8s-5-141 /]# mkdir /data/k8s-yaml/coredns
#重启nginx
[root@k8s-5-141 /]# nginx -t
[root@k8s-5-141 /]# nginx -s reload
1.2 创建 pod 定义模板
# cm.yaml
[root@k8s-5-141 /]# vim /data/k8s-yaml/coredns/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 . 192.168.5.140
cache 30
loop
reload
loadbalance
}
# dp.yaml
[root@k8s-5-141 /]# vim /data/k8s-yaml/coredns/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:1.7.0
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
#rbac.yaml
[root@k8s-5-141 /]# vim /data/k8s-yaml/coredns/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
#svc.yaml
[root@k8s-5-141 /]# vim /data/k8s-yaml/coredns/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
1.3 设置 dns
在 k8s-5-140 服务器上操作
[root@k8s-5-140 ~]# vim /var/named/od.com.zone
$ORIGIN od.com.
$TTL 600 ; 10 minutes
@ IN SOA dns.od.com. dnsadmin.od.com. (
2021031605 ; serial
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 192.168.5.140
harbor A 192.168.5.141
k8s-yaml A 192.168.5.141 #增加这一行
# 重启named服务
[root@k8s-5-140 ~]# systemctl restart named
[root@k8s-5-140 ~]# dig -t A k8s-yaml.od.com @192.168.5.140 +short
192.168.5.141
二、下载coredns镜像
在任何一台安装有docker的服务器上操作都行, 我为了验证k8s集群自动部署的效果,所以在运维主机上操作的
[root@k8s-5-141 /]# docker pull coredns/coredns:1.7.0
1.7.0: Pulling from coredns/coredns
Digest: sha256:73ca82b4ce829766d4f1f10947c3a338888f876fbed0540dc849c89ff256e90c
Status: Image is up to date for coredns/coredns:1.7.0
docker.io/coredns/coredns:1.7.0
[root@k8s-5-141 /]# docker images |grep coredns
coredns/coredns 1.7.0 bfe3a36ebd25 9 months ago 45.2MB
[root@k8s-5-141 /]# docker tag bfe3a36ebd25 harbor.od.com/public/coredns:1.7.0
[root@k8s-5-141 /]# docker images |grep coredns
coredns/coredns 1.7.0 bfe3a36ebd25 9 months ago 45.2MB
harbor.od.com/public/coredns 1.7.0 bfe3a36ebd25 9 months ago 45.2MB
[root@alice001 ~]# docker push harbor.od.com/public/coredns:1.7.0
docker push harbor.od.com/public/coredns:1.7.0
The push refers to repository [harbor.od.com/public/coredns]
da1ec456edc8: Pushed
225df95e717c: Pushed
1.7.0: digest: sha256:c7bf0ce4123212c87db74050d4cbab77d8f7e0b49c041e894a35ef15827cf938 size: 739
三、部署 coredns
在任意一台k8s节点服务器上操作
[root@k8s-5-138 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/rbac.yaml
serviceaccount/coredns created
clusterrole.rbac.authorization.k8s.io/system:coredns created
clusterrolebinding.rbac.authorization.k8s.io/system:coredns created
[root@k8s-5-138 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/cm.yaml
configmap/coredns created
[root@k8s-5-138 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/dp.yaml
deployment.apps/coredns created
[root@k8s-5-138 ~]# kubectl apply -f http://k8s-yaml.od.com/coredns/svc.yaml
service/coredns created
四、验证
[root@k8s-5-138 ~]# dig -t A www.baidu.com @192.168.0.2 +short
www.a.shifen.com.
14.215.177.38
14.215.177.39
[root@k8s-5-138 ~]# kubectl get svc
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
kubernetes ClusterIP 192.168.0.1 <none> 443/TCP 7d
nginx-web ClusterIP 192.168.200.143 <none> 80/TCP 20h
[root@k8s-5-138 ~]# kubectl get svc -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
coredns ClusterIP 192.168.0.2 <none> 53/UDP,53/TCP,9153/TCP 20h
[root@k8s-5-138 ~]# dig -t A nginx-web.default.svc.cluster.local @192.168.0.2 +short
192.168.200.143
#部署应用,检查是否可以通过
[root@alice002 ~]# kubectl create deployment nginx-ds --image=harbor.od.com/public/nginx:v1.7.9
deployment.apps/nginx-ds created
[root@alice002 ~]# kubectl expose deployment nginx-ds --port=80 --target-port=80
service/nginx-web exposed