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
@bowei, Thanks for the feature to add nameserver to kubedns via stubDomains, its really useful.
I find that nameserver need to be pure ip and does not support appending with port.
it would be really useful to support nameserver appended with port, if somebody wants to deploy dns-server in kubernetes as a NodePort service and there could be possibilities where cloud-provider may not be supporting LoadBalancer type service.
We do have a use case in federation for federating clusters on non-cloud environments.
if agree, i can send a patch to support nameserver appended with port number
cc @kubernetes/sig-federation-misc
The text was updated successfully, but these errors were encountered:
@bowei, Thanks for the feature to add nameserver to kubedns via stubDomains, its really useful.
I find that nameserver need to be pure ip and does not support appending with port.
it would be really useful to support nameserver appended with port, if somebody wants to deploy dns-server in kubernetes as a NodePort service and there could be possibilities where cloud-provider may not be supporting LoadBalancer type service.
We do have a use case in federation for federating clusters on non-cloud environments.
if agree, i can send a patch to support nameserver appended with port number
cc @kubernetes/sig-federation-misc
The text was updated successfully, but these errors were encountered: