向Kubernetes集群域名服务器中插入自定义的解析记录-coredns
2021-01-16 08:11
标签:loop pod edit config ping app elf dns 解析 找到kube-system命名空间的名称为coredns的configmap: ? ~ ? kubectl edit configmap coredns -n kube-system 重启coredns: ~ ? kubectl scale deployment coredns -n kube-system --replicas=0 ~ ? kubectl scale deployment coredns -n kube-system --replicas=2 向Kubernetes集群域名服务器中插入自定义的解析记录-coredns 标签:loop pod edit config ping app elf dns 解析 原文地址:https://blog.51cto.com/13534471/2513355
注意:从Kubenretes 1.14开始,集群内部的域名服务器默认换成了coredns
? kubectl get configmap coredns -n kube-system
NAME DATA AGE
coredns 1 9d
编辑这个configmap:
编辑为以下内容(添加了hosts块):apiVersion: v1
data:
Corefile: |
.:53 {
errors
health
kubernetes cluster.local in-addr.arpa ip6.arpa {
pods insecure
upstream
fallthrough in-addr.arpa ip6.arpa
ttl 30
}
hosts {
10.10.10.10 www.baidu.com
10.10.10.11 www.baidu.cn #添加记录
}
prometheus :9153
forward . "/etc/resolv.conf"
cache 30
loop
reload
loadbalance
}
kind: ConfigMap
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"v1","data":{"Corefile":".:53 {\n errors\n health\n kubernetes cluster.local in-addr.arpa ip6.arpa {\n pods insecure\n upstream\n fallthrough in-addr.arpa ip6.arpa\n ttl 30\n }\n prometheus :9153\n forward . \"/etc/resolv.conf\"\n cache 30\n loop\n reload\n loadbalance\n}\n"},"kind":"ConfigMap","metadata":{"annotations":{},"labels":{"addonmanager.kubernetes.io/mode":"EnsureExists"},"name":"coredns","namespace":"kube-system"}}
creationTimestamp: "2019-08-19T09:14:15Z"
labels:
addonmanager.kubernetes.io/mode: EnsureExists
name: coredns
namespace: kube-system
resourceVersion: "3231349"
selfLink: /api/v1/namespaces/kube-system/configmaps/coredns
uid: b791c47f-c261-11e9-b426-525400116042
deployment.extensions/coredns scaled
deployment.extensions/coredns scaled
测试,进入任意一个具有ping命令的pod中,ping自己插入的域名,能通就说明已经生效了。
文章标题:向Kubernetes集群域名服务器中插入自定义的解析记录-coredns
文章链接:http://soscw.com/index.php/essay/42620.html