Switch to wildcard DNS entry for service names in example

[dastbe]

Because we still require some DNS entry for applications to resolve some IP before it will make a request that envoy can proxy, the examples end up duplicating names across service discovery and router service names/backends. This leads to confusion because it's implied there's some coordination between the two when there isn't.

We can fix our example apps by creating a private hosted zone for "#{meshName}.appmesh" with a wildcard entry to any IP. VirtualRouters will register on "colorgateway.#{meshName}.appmesh" and "colorteller.#{meshName}.appmesh" and the actual VNode service discovery can use existing kubedns/CloudMap names. I would expect this would be how we recommend customers configure things as well until we have a better solution for the DNS hole.

[kiranmeduri]

I agree, made use of this pattern in howto-ecs-basics walkthrough

aws-app-mesh-examples/walkthroughs/howto-ecs-basics/deploy/2-meshify.yaml

Line 290 in bdd7323

AppMeshWildcardRecordSet:

[kiranmeduri]

Changing other examples may be not necessary, closing this.