Fix Ambassador install instructions to avoid panic (#1893)

* Fix Ambassador install instructions to avoid panic

This commit installs Ambassador using ambassador-rbac.yaml instead
of ambassador-knative.yaml which will be deprecated soon.

ambassador-rbac.yaml contains the latest Ambassador install
manifests which have sufficient RBAC to update ingress resources
when required. ambassador-knative.yaml does not have these
permissions and hence Ambassador panics for anyone who follows
the instructions.

* Docs to install Ambassador in a separate namespace

This commit adds instructions to install Ambassador in a different
namespace. By default, Ambassador installs in "default" namespace.
This commit is contained in:
Shubham 2020-01-07 03:38:50 +05:30 committed by Knative Prow Robot
parent bbda7cf64b
commit 23b2a801a6
1 changed files with 26 additions and 6 deletions

View File

@ -55,11 +55,31 @@ service mesh.
You can install Ambassador with `kubectl`:
```
kubectl apply \
--filename https://getambassador.io/yaml/ambassador/ambassador-knative.yaml \
--filename https://getambassador.io/yaml/ambassador/ambassador-service.yaml
```
1. Create a namespace to install Ambassador in:
```
kubectl create namespace ambassador
```
2. Install Ambassador:
```
kubectl apply --namespace ambassador \
--filename https://getambassador.io/yaml/ambassador/ambassador-rbac.yaml \
--filename https://getambassador.io/yaml/ambassador/ambassador-service.yaml
```
3. Give Ambassador the required permissions:
```
kubectl patch clusterrolebinding ambassador -p '{"subjects":[{"kind": "ServiceAccount", "name": "ambassador", "namespace": "ambassador"}]}'
```
4. Enable Knative support in Ambasssador:
```
kubectl set env --namespace ambassador deployments/ambassador AMBASSADOR_KNATIVE_SUPPORT=true
```
## Configuring DNS
@ -71,7 +91,7 @@ before DNS may be set up.
Get this external IP address with:
```
$ kubectl get svc ambassador
$ kubectl get service ambassador -n ambassador
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
ambassador LoadBalancer 10.59.246.30 35.229.120.99 80:32073/TCP 13m