You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this an ISSUE or FEATURE REQUEST? (choose one): Issue
Which release version?: 1.0.7
Which component (CNI/IPAM/CNM/CNS): CNI
Which Operating System (Linux/Windows): Windows Server version 1803 (17134)
Which Orchestrator and version (e.g. Kubernetes, Docker): Kubernetes v1.11.1
What happened:
Windows pods still only get the dns search suffix for their namespace. They should also have svc.cluster.local and cluster.local so that services can be resolved for other namespaces.
This is somewhat related to #146. That PR added the pod's namespace, but not the others. If you need more info on what needs to change, please check with @dineshgovindasamy and @daschott
The text was updated successfully, but these errors were encountered:
Is this an ISSUE or FEATURE REQUEST? (choose one): Issue
Which release version?: 1.0.7
Which component (CNI/IPAM/CNM/CNS): CNI
Which Operating System (Linux/Windows): Windows Server version 1803 (17134)
Which Orchestrator and version (e.g. Kubernetes, Docker): Kubernetes v1.11.1
What happened:
Windows pods still only get the dns search suffix for their namespace. They should also have
svc.cluster.local
andcluster.local
so that services can be resolved for other namespaces.Here's
/etc/resolv.conf
on LinuxWindows should have the same DNS search suffix results, but it only has the current namespace:
How to reproduce it (as minimally and precisely as possible):
kubectl apply -f https://gist.githubusercontent.com/PatrickLang/0df013d20d32eb98bc57456c4f73461a/raw/052470dc51c9d3582e85e370d2fb1adca78345af/iis-1803-healthcheck.yaml
kubectl get pod
- find the pod once its runningkubectl exec podname ipconfig
Anything else we need to know:
This is somewhat related to #146. That PR added the pod's namespace, but not the others. If you need more info on what needs to change, please check with @dineshgovindasamy and @daschott
The text was updated successfully, but these errors were encountered: