Minor formatting fixes
This commit is contained in:
parent
a18294d417
commit
85ab0e6e70
1 changed files with 4 additions and 4 deletions
|
@ -679,7 +679,7 @@ spec:
|
||||||
[examples/k8s/cheese-ingress.yaml](https://github.com/containous/traefik/tree/master/examples/k8s/cheese-ingress.yaml)
|
[examples/k8s/cheese-ingress.yaml](https://github.com/containous/traefik/tree/master/examples/k8s/cheese-ingress.yaml)
|
||||||
|
|
||||||
!!! note
|
!!! note
|
||||||
we list each hostname, and add a backend service.
|
We list each hostname, and add a backend service.
|
||||||
|
|
||||||
```shell
|
```shell
|
||||||
kubectl apply -f https://raw.githubusercontent.com/containous/traefik/master/examples/k8s/cheese-ingress.yaml
|
kubectl apply -f https://raw.githubusercontent.com/containous/traefik/master/examples/k8s/cheese-ingress.yaml
|
||||||
|
@ -783,11 +783,11 @@ Traefik will now look for cheddar service endpoints (ports on healthy pods) in b
|
||||||
Deploying cheddar into the cheese namespace and afterwards shutting down cheddar in the default namespace is enough to migrate the traffic.
|
Deploying cheddar into the cheese namespace and afterwards shutting down cheddar in the default namespace is enough to migrate the traffic.
|
||||||
|
|
||||||
!!! note
|
!!! note
|
||||||
The kubernetes documentation does not specify this merging behavior.
|
The kubernetes documentation does not specify this merging behavior.
|
||||||
|
|
||||||
!!! note
|
!!! note
|
||||||
Merging ingress definitions can cause problems if the annotations differ or if the services handle requests differently.
|
Merging ingress definitions can cause problems if the annotations differ or if the services handle requests differently.
|
||||||
Be careful and extra cautious when running multiple overlapping ingress definitions.
|
Be careful and extra cautious when running multiple overlapping ingress definitions.
|
||||||
|
|
||||||
## Specifying Routing Priorities
|
## Specifying Routing Priorities
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue