Support Kubernetes DNS resolver

[stefanprodan]

App Mesh virtual services should behave similar to the Kubernetes DNS resolver. If I create a virtual service called backend in the test namespace, the backend app should be reachable inside the mesh at the following addresses:

• http://backend (if the caller is in the same namespace as the virtual service)
• http://backend.test
• http://backend.test.svc.cluster.local

[nckturner]

For this, I think we should create multiple virtual services in the App Mesh API, and give them all the same virtual router provider. For example, if the user creates a virtual service called backend in the test namespace, (AND there is a Kubernetes service called backend in the test namespace) then we should also create backend.test, backend.test.svc, and backend.test.svc.cluster.local.

I'm basing this off the contents of the resolv.conf in a pod in my cluster:

# cat /etc/resolv.conf
nameserver 10.100.0.10
search appmesh-demo.svc.cluster.local svc.cluster.local cluster.local us-west-2.compute.internal
options ndots:5

[stefanprodan]

If all virtual services will use the same virtual router that should work fine.

[ar4096]

@Y0Username @cgchinmay Lets review this issue to see what the customer ask is.