istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

fix-up some broken url (#5746)

This commit is contained in:
chentanjun 2019-11-16 21:24:43 +08:00 committed by Istio Automation
parent 7cb3882cf5
commit 4a6cc71dcd
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -51,7 +51,7 @@ is used is determined by the istio.io [Netlify](https://netlify.com) project's c
- The content of archive.istio.io is taken from the older release-XXX branches. The set of branches that
are included on archive.istio.io is determined by the `TOBUILD` variable in this
[script](https://github.com/istio/istio.io/blob/master/scripts/gen_archive_site.sh).
[script](https://github.com/istio/istio.io/blob/master/scripts/build_archive_site.sh).
### Publishing content immediately

2
content/en/blog/2019/data-plane-setup/index.md
View File

@ -33,7 +33,7 @@ It is important to understand that the sidecar injection into the application po
In simple terms, sidecar injection is adding the configuration of additional containers to the pod template. The added containers needed for the Istio service mesh are:
`istio-init`
This [init container] (<https://kubernetes.io/docs/concepts/workloads/pods/init-containers/>) is used to setup the `iptables` rules so that inbound/outbound traffic will go through the sidecar proxy. An init container is different than an app container in following ways:
This [init container](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) is used to setup the `iptables` rules so that inbound/outbound traffic will go through the sidecar proxy. An init container is different than an app container in following ways:
- It runs before an app container is started and it always runs to completion.
- If there are many init containers, each should complete with success before the next container is started.