No Outbound connections from Windows containers in Kubernetes cluster

[RajaAyyapusetty]

Is this a request for help?:

Yes

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

ISSUE

What version of acs-engine?:

0.16.0

Orchestrator and version (e.g. Kubernetes, DC/OS, Swarm)
Kubernetes 1.10.1

What happened:
I've setup a Kubernetes 1.10.1 cluster with support for Hyper-V isolation using below 2 links:
https://gist.github.com/PatrickLang/2cf4b81c9518e531b828a71e4c430332
#2627

After acs-engine is finished with cluster creation, I installed the KB specified in the first link and restarted kubelet. I'm able to run the containers with HyperV isolation fine but from the container can't make any outbound connections. Here's the output from Invoke-WebRequest:

Invoke-WebRequest -Uri www.google.com -UseBasicParsing
Invoke-WebRequest : The remote name could not be resolved: 'www.google.com'
At line:1 char:1

• Invoke-WebRequest -Uri www.google.com -UseBasicParsing

•   + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
   eption
    + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
  
  

What you expected to happen:
Access resources outside of the cluster successfully.

How to reproduce it (as minimally and precisely as possible):
Create kubernetes 1.10.1 cluster using acs-engine 0.16 with support for Hyper-V. Patch Windows nodes with KB4093112. Create a Pod with HyperV isolation enabled. Exec into the container and ping any url.

Anything else we need to know:
Our image is derived from microsoft/windowsservercore (ltsc)

[PatrickLang]

This may be fixed by Azure/azure-container-networking#127

[saiyan86]

#2822 will fix this.