dns not in ready state with public IP addresses

[ibalajiarun]

I have a 2-node microk8s setup in Azure composed of two regions. The only way for the nodes to communicate is through public IPs. I have enabled the dns addon, but it does not enter READY state. The dns pod is located at the non-master node. The following is the log from the pod:

E0102 22:18:28.833793       1 reflector.go:134] pkg/mod/k8s.io/client-go@v10.0.0+incompatible/tools/cache/reflector.go:95: Failed to list *v1.Endpoints: Get https://10.152.183.1:443/api/v1/endpoints?limit=500&resourceVersion=0: dial tcp 10.152.183.1:443: i/o timeout
E0102 22:18:28.834859       1 reflector.go:134] pkg/mod/k8s.io/client-go@v10.0.0+incompatible/tools/cache/reflector.go:95: Failed to list *v1.Namespace: Get https://10.152.183.1:443/api/v1/namespaces?limit=500&resourceVersion=0: dial tcp 10.152.183.1:443: i/o timeout
E0102 22:18:28.842780       1 reflector.go:134] pkg/mod/k8s.io/client-go@v10.0.0+incompatible/tools/cache/reflector.go:95: Failed to list *v1.Service: Get https://10.152.183.1:443/api/v1/services?limit=500&resourceVersion=0: dial tcp 10.152.183.1:443: i/o timeout

I know it is related to #845 #871 but I opened a new issue because I think it may be because my setup uses public IPs. Any ideas on how I go about solving this?

inspection-report-20200102_212510.tar.gz

[ibalajiarun]

I think this is due to the design of Kubernetes: it requires nodes to be in a private network.