Fix formatting issues in federated ingress docs
This commit is contained in:
committed by
Andrew Chen
parent
5462769c4a
commit
d3242d6a23
@@ -110,7 +110,7 @@ You can verify this by checking in each of the underlying clusters, for example:
|
|||||||
``` shell
|
``` shell
|
||||||
kubectl --context=gce-asia-east1a get ingress myingress
|
kubectl --context=gce-asia-east1a get ingress myingress
|
||||||
NAME HOSTS ADDRESS PORTS AGE
|
NAME HOSTS ADDRESS PORTS AGE
|
||||||
myingress * 130.211.5.194 80, 443 1m
|
myingress * 130.211.5.194 80, 443 1m
|
||||||
```
|
```
|
||||||
|
|
||||||
The above assumes that you have a context named 'gce-asia-east1a'
|
The above assumes that you have a context named 'gce-asia-east1a'
|
||||||
@@ -172,7 +172,7 @@ ingresses function correctly, either start with new, empty clusters, or make
|
|||||||
sure that you delete (and recreate if necessary) all pre-existing
|
sure that you delete (and recreate if necessary) all pre-existing
|
||||||
Ingresses in the clusters comprising your federation.
|
Ingresses in the clusters comprising your federation.
|
||||||
|
|
||||||
#Adding backend services and pods
|
## Adding backend services and pods
|
||||||
|
|
||||||
To render the underlying ingress shards healthy, we need to add
|
To render the underlying ingress shards healthy, we need to add
|
||||||
backend Pods behind the service upon which the Ingress is based. There are several ways to achieve this, but
|
backend Pods behind the service upon which the Ingress is based. There are several ways to achieve this, but
|
||||||
@@ -187,7 +187,7 @@ kubectl --context=federation-cluster create -f services/nginx.yaml
|
|||||||
```
|
```
|
||||||
|
|
||||||
``` shell
|
``` shell
|
||||||
kubectl --context=federation-cluster create -f myreplicaset.yaml
|
kubectl --context=federation-cluster create -f myreplicaset.yaml
|
||||||
```
|
```
|
||||||
|
|
||||||
Note that in order for your federated ingress to work correctly on
|
Note that in order for your federated ingress to work correctly on
|
||||||
|
|||||||
Reference in New Issue
Block a user