Public IP fronting a k8s Service has no DNS name in ACS

9/15/2017

I've created a k8s Service to publicly front my WebApi pod in my ACS Windows cluster. It works great but there is no DNS name associated with the Public IP resources that is created. This prohibits me from adding it as an endpoint for a Traffic Manager profile, roadblock!

I can manually assign a DNS name to the Public IP, but then I'd be touching an ACS created resource, which makes me uncomfortable. But I REALLY want a static DNS name and the features of TrafficMgr to be in front of it.

This feels like a significant deficiency. Any advice?

-- BrettRobi
azure-container-service
kubernetes

2 Answers

9/15/2017

When you create a service, Kubernete automatically create a dns for it as long as kube-dns is running. The service name becomes the dns for accessing the pod withing the cluster and resolves to the cluster IP. So you can use the service name within other pods in the cluster.

https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#dns

-- Innocent Anigbo
Source: StackOverflow

9/15/2017

there is a feature request in upstream https://github.com/kubernetes/kubernetes/issues/50062

-- Weinong Wang
Source: StackOverflow