Skip to content
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

DNS search suffix not for namespace on Windows pods #146

Closed
PatrickLang opened this issue May 24, 2018 · 2 comments
Closed

DNS search suffix not for namespace on Windows pods #146

PatrickLang opened this issue May 24, 2018 · 2 comments
Assignees

Comments

@PatrickLang
Copy link
Contributor

PatrickLang commented May 24, 2018

Is this an ISSUE or FEATURE REQUEST? (choose one):

Issue

Which release version?:

v1.0.4-1-gf0f090e

Which component (CNI/IPAM/CNM/CNS):

CNI

Which Operating System (Linux/Windows):

Windows Server version 1803

Which Orchestrator and version (e.g. Kubernetes, Docker)

Kubernetes

What happened:

The DNS suffix is not set based on the pod's namespace.

What you expected to happen:

On Linux, we see the right resolution order.

/etc # cat resolv.conf
nameserver 10.0.0.10
search default.svc.cluster.local svc.cluster.local cluster.local lje1130gi5iehkdbexza4ptcba.xx.internal.cloudapp.net

Windows only has svc.cluster.local

How to reproduce it (as minimally and precisely as possible):

Deploy a Windows cluster with acs-engine v0.17

@saiyan86
Copy link
Contributor

saiyan86 commented Jun 9, 2018

This is fixed in PR #152 add k8s pod namespace to dns suffix

@saiyan86 saiyan86 closed this as completed Jun 9, 2018
@daschott
Copy link

@saiyan86 I see this issue again on acs-engine v0.18.9 Since you did #152 are you on point for fixing this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants