fix 404 urls in docs

This commit is contained in:
tanjunchen 2019-11-18 14:24:22 +08:00
parent baa5ae3934
commit b67a656ece
3 changed files with 3 additions and 3 deletions

View File

@ -7,7 +7,7 @@ creates AWS Application Load Balancer (ALB) that is used to terminate TLS connec
certificates. ALBs are used to route traffic to an Ingress http router for example certificates. ALBs are used to route traffic to an Ingress http router for example
[skipper](https://github.com/zalando/skipper/), which routes [skipper](https://github.com/zalando/skipper/), which routes
traffic to Kubernetes services and implements traffic to Kubernetes services and implements
[advanced features](https://zalando.github.io/skipper/dataclients/kubernetes/) [advanced features](https://opensource.zalando.com/skipper/kubernetes/ingress-controller/)
like green-blue deployments, feature toggles, rate limits, like green-blue deployments, feature toggles, rate limits,
circuitbreakers, metrics, access logs, opentracing API, shadow traffic or A/B tests. circuitbreakers, metrics, access logs, opentracing API, shadow traffic or A/B tests.

View File

@ -125,7 +125,7 @@ flags. Using these flags, you can do:
export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Performance\]" export GINKGO_TEST_ARGS="--ginkgo.focus=\[Feature:Performance\]"
``` ```
and follow the instructions above. [Here are some other examples from the `e2e.go` documentation.](https://github.com/kubernetes/community/blob/master/contributors/devel/e2e-tests.md#building-and-running-the-tests). and follow the instructions above. [Here are some other examples from the `e2e.go` documentation.](https://github.com/kubernetes/community/blob/master/contributors/devel/sig-testing/e2e-tests.md).
If you want to test against an existing cluster, you can do: If you want to test against an existing cluster, you can do:

View File

@ -249,7 +249,7 @@ This has been solved in kops 1.9.0, when creating a new cluster no action is nee
### Canal Example for CNI and Network Policy ### Canal Example for CNI and Network Policy
Canal is a project that combines [Flannel](https://github.com/coreos/flannel) and [Calico](http://docs.projectcalico.org/latest/getting-started/kubernetes/installation/hosted/) for CNI Networking. It uses Flannel for networking pod traffic between hosts via VXLAN and Calico for network policy enforcement and pod to pod traffic. Canal is a project that combines [Flannel](https://github.com/coreos/flannel) and [Calico](http://docs.projectcalico.org/latest/getting-started/kubernetes/installation/) for CNI Networking. It uses Flannel for networking pod traffic between hosts via VXLAN and Calico for network policy enforcement and pod to pod traffic.
#### Installing Canal on a new Cluster #### Installing Canal on a new Cluster