Added example to show how to use service behind ALB as a virtual-service #202
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Related to #119
Description of changes:
This example provides a basic setup where there is a external facing ALB that forwards traffic to a target-group that is also registered as virtual-node with App Mesh. This virtual-node (front) uses backend that is registered as virtual-service. This virtual-service uses virtual-router that forwards traffic to virtual-node v1 that is behind an internal ALB (just to show how traffic can be routed to ALB backed service) and virtual-node v2 that uses Cloud Map service-discovery.
This is a contrived example to show that it is possible to get this up and running. However, it is not a good user-experience, application need to register with ALB target-group, Cloud Map service-discovery and App Mesh virtual-node. It is preferable to use a single pane API.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.