54a4ac9f84
DNS service is a very critical service in k8s world, though it's not a part of k8s itself. So it would be nice to have it replicate more than 1 and on differents nodes to have high availbility. Otherwise, services running on k8s cluster will be broken if the node contains DNS pod down. Another sample is, when user would like to do a cluster upgrade, services will be borken when the node containers DNS pod being replaced. You can find lots of discussion about this, please refer [1],[2] and [3]. [1] https://github.com/kubernetes/kubeadm/issues/128 [2] https://github.com/kubernetes/kubernetes/issues/40063 [3] https://github.com/kubernetes/kops/issues/2693 Closes-Bug: #1757554 Change-Id: Ic64569d4bdcf367955398d5badef70e7afe33bbb
9 lines
316 B
YAML
9 lines
316 B
YAML
---
|
|
issues:
|
|
- |
|
|
Currently, the replicas of coreDNS pod is hardcoded as 1. It's not a
|
|
reasonable number for such a critical service. Without DNS, probably all
|
|
workloads running on the k8s cluster will be broken. Now Magnum is making
|
|
the coreDNS pod autoscaling based on the nodes and cores number.
|
|
|