Skip to content

Commit

Permalink
add documentation for ambassador_id support
Browse files Browse the repository at this point in the history
  • Loading branch information
phsiao committed Aug 21, 2019
1 parent 7860f87 commit ec2e5fc
Showing 1 changed file with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions doc/source/ingress/ambassador.md
Original file line number Diff line number Diff line change
Expand Up @@ -102,6 +102,27 @@ A worked example for [header based routing](../examples/ambassador_headers.html)

To understand more about the Ambassador configuration for this see [their docs on header based routing](https://www.getambassador.io/reference/headers).

## Multiple Ambassadors in the same cluster

To avoid conflicts in a cluster with multiple ambassadors running, you can add the following annotation to your Seldon Deployment resource.

* `seldon.io/ambassador-id:<instance id>`: The instance id to be added to Ambassador `ambassador_id` configuration

For example,

```YAML
apiVersion: machinelearning.seldon.io/v1alpha2
kind: SeldonDeployment
metadata:
name: multi-ambassadors
spec:
annotations:
seldon.io/ambassador-id: my_instance
name: ambassadors-example
```
Note that your Ambassador instance must be configured with matching `ambassador_id`.
See [AMBASSADOR_ID](https://github.com/datawire/ambassador/blob/master/docs/reference/running.md#ambassador_id) for details

## Custom Amabassador configuration

Expand Down

0 comments on commit ec2e5fc

Please sign in to comment.