Add CoreDNS to kubernetes drivers
Bug #1692449 reported by
Spyros Trigazis
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
Fix Released
|
High
|
Ricardo Rocha |
Bug Description
A very important feature for kubernetes driver is a DNS add-on.
After discussion in the Boston summit, we decided to choose CoreDNS, a project embraced by the CNCF foundation.
[1] https:/
[2] https:/
Changed in magnum: | |
assignee: | nobody → Ricardo Rocha (rocha-porto) |
status: | New → Confirmed |
importance: | Undecided → High |
Changed in magnum: | |
status: | Confirmed → In Progress |
Changed in magnum: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/462181 /git.openstack. org/cgit/ openstack/ magnum/ commit/ ?id=7c35c8fe40e c2b012696965e22 5d2b2d6ea0f6b1
Committed: https:/
Submitter: Jenkins
Branch: master
commit 7c35c8fe40ec2b0 12696965e225d2b 2d6ea0f6b1
Author: Ricardo Rocha <email address hidden>
Date: Wed May 3 16:46:06 2017 +0200
Add CoreDNS deployment in kubernetes atomic
Enable internal cluster DNS by deploying CoreDNS in the kube-system
namespace. It covers dns queries for both the cluster and external,
acting as a proxy with a cache layer in front.
Version of CoreDNS hard-coded to 007, image taken from dockerhub.
Related-Bug: #1692449
Change-Id: I0a9703b531fe87 2416dcd79fa7d4d 27c1ea61586