-
Notifications
You must be signed in to change notification settings - Fork 40k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch DNS addons from skydns to kubedns #26335
Switch DNS addons from skydns to kubedns #26335
Conversation
56e2ca9
to
15b85b1
Compare
name: dns-tcp | ||
protocol: TCP | ||
- name: healthz | ||
image: gcr.io/google_containers/exechealthz:1.0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
exechealthz-amd64:1.0
Can you update the RELEASE guide with how to build a new image (there's one in the kube2sky subdir, not sure how we want to documenting releasing this though, maybe add it to build/kube-dns?), and add a comment in skydns.rc that it's deprecated. I'd also prefer just having one kubedns.rs, so maybe remove the deployment in cluster/saltbase for now? |
lgtm once you've addressed comments from @luxas |
Noticed a new merge to master - some more changes to the kubedns-rc saltbase files. @ArtfulCoder - after the switch to GCI images, the new kubedns pod is running anymore when I do kube-up. Its running the old skydns pod. I am trying to fix the files in the addons directory and cluster-helper to switch to kube-dns. |
|
@@ -0,0 +1,80 @@ | |||
apiVersion: v1 | |||
kind: ReplicationController |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isn't this basically the same as cluster/saltbase/salt/kube-dns/kubedns-rc.yaml.in ? Why do we need both? Can we just kill off cluster/addons/dns and leave a pointer to the new location?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also see #25020
I'm all for expedient solutions, but this seems redundant, doesn't it? can we discuss quickly today? |
@thockin |
15b85b1
to
7bc2c82
Compare
Was labelled XXL because of the large deletions of deprecated kube2sky and skydns directories. |
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. | ||
# See the License for the specific language governing permissions and | ||
# limitations under the License. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if you're doing this anyway why not just get rid of addons and move to cluster/saltbase instead? (IMO addons/ for DNS is confusing, and I thought previously you wanted to keep the change small)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tim suggested the same (remove from 'addons')
I am deleting the cluster/addons/dns directory completely and moving templates to saltbase and build code to build/kube-dns.
35fccde
to
4825497
Compare
@@ -189,7 +189,7 @@ KUBE_DNS_DOMAIN="cluster.local" | |||
KUBE_DNS_REPLICAS=1 | |||
``` | |||
|
|||
To know more on DNS service you can look [here](http://issue.k8s.io/6667). Related documents can be found [here](../../cluster/addons/dns/#how-do-i-configure-it) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you also update local-up-cluster?
If it's not just a simple rename, I'm fine with a follow up, as long as you add a todo somewhere. I don't want people to see skydns as a pod name when they do kubectl get pods because that's misleading. I think we should get this in asap so we can start testing it asap, hopefully before we cut the branch. |
@@ -53,7 +71,7 @@ spec: | |||
timeoutSeconds: 5 | |||
args: | |||
# command = "/kube-dns" | |||
- --domain={{ pillar['dns_domain'] }}. | |||
- --domain={{ pillar['dns_domain'] }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
are you removing the "." ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch...the . needs to be there.
This is your issue if you need a unittest rerun and are not going to upload a new pr (#26578) |
Oh thanks...I didn't see the test failure - it seems like it was a flake, I will submit the review changes and rerun the tests. |
We should fix the v13 x image: 1.2 offset, but not necessarily in this pr since there will be more pushes. I also guess this doesn't need a release note since we're adding one for the inital kube-dns. |
Marking p2 since DNS is currently getting no test coverage |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 555b900. |
Automatic merge from submit-queue |
fix godeps on master broken in #26335
Change GCI and trusty cluster-helper scripts to use kubedns instead of skydns.