Skip to content

Commit

Permalink
Add App Mesh backend example
Browse files Browse the repository at this point in the history
  • Loading branch information
stefanprodan committed Mar 24, 2019
1 parent 8a981f9 commit 1912286
Showing 1 changed file with 17 additions and 0 deletions.
17 changes: 17 additions & 0 deletions docs/gitbook/usage/appmesh-progressive-delivery.md
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,9 @@ spec:
port: 9898
# App Mesh reference
meshName: global.appmesh-system
# App Mesh egress (optional)
backends:
- backend.test
# define the canary analysis timing and KPIs
canaryAnalysis:
# schedule interval (default 60s)
Expand Down Expand Up @@ -119,6 +122,20 @@ virtualnode.appmesh.k8s.aws/podinfo-primary
virtualservice.appmesh.k8s.aws/podinfo.test
```

The App Mesh specific settings are:

```yaml
service:
port: 9898
meshName: global.appmesh-system
backends:
- backend1.test
- backend2.test
```
App Mesh blocks all egress traffic by default. If your application needs to call another service, you have to create an
App Mesh virtual service for it and add the virtual service name to the backend list.
### Setup App Mesh ingress
In order to expose the podinfo app outside the mesh you'll be using an Envoy ingress and an AWS classic load balancer.
Expand Down

0 comments on commit 1912286

Please sign in to comment.