From 03698e0099f5147f5d26adbe1b92ab4d0fbcd2d4 Mon Sep 17 00:00:00 2001 From: mtail Date: Fri, 8 Mar 2019 19:21:01 -0800 Subject: [PATCH] Fix bad URL syntax, surfaced by my previous fix to the {{ tip }} stuff --- content/blog/2019/data-plane-setup/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2019/data-plane-setup/index.md b/content/blog/2019/data-plane-setup/index.md index 8c82ee3181..b0c482f90a 100644 --- a/content/blog/2019/data-plane-setup/index.md +++ b/content/blog/2019/data-plane-setup/index.md @@ -347,5 +347,5 @@ The output above clearly shows that all the incoming traffic to port 80, which i This brings us to the end of this post. I hope it helped to de-mystify how Istio manages to inject the sidecar proxies into an existing deployment and how Istio routes the traffic to the proxy. {{< idea >}} -Update: In place of `istio-init`, there now seems to be an option of using the new CNI, which removes the need for the init container and associated privileges. This [`istio-cni`] () plugin sets up the pods' networking to fulfill this requirement in place of the current Istio injected pod `istio-init` approach. +Update: In place of `istio-init`, there now seems to be an option of using the new CNI, which removes the need for the init container and associated privileges. This [`istio-cni`](https://github.com/istio/cni) plugin sets up the pods' networking to fulfill this requirement in place of the current Istio injected pod `istio-init` approach. {{< /idea >}}