Resolve "Create Templates for Istio-CNI"

General MR

Summary

• Added istio-cni

Relevant logs/screenshots

Command to ensure istio-cni is in effect

kubectl get pods -A -o jsonpath='{.items[*].spec.initContainers[*].name}' | grep istio-init

With istio-cni in place there is no longer a need for the istio-init container and will be replaced by the istio-validation container:

kubectl get pods -A -o jsonpath='{.items[*].spec.initContainers[*].name}' | grep istio-validation

Refer to upgrade notice in regards to validating this in an already installed Big Bang deployment

➜  ~ kubectl get po -n kube-system
NAME                                      READY   STATUS    RESTARTS   AGE
coredns-5688667fd4-d92mf                  1/1     Running   0          14m
istio-cni-node-5sg22                      1/1     Running   0          5m45s
istio-cni-node-k2pwc                      1/1     Running   0          5m45s
istio-cni-node-kxn8z                      1/1     Running   0          5m45s
istio-cni-node-rr6rz                      1/1     Running   0          5m45s
local-path-provisioner-774c6665dc-lrnhw   1/1     Running   0          15m

Linked Issue

issue

Upgrade Notices

If you are enabling the istio-cni in an existing environment all workloads will need to be restarted to ensure they are using it. The following command can be used to accomplish this:

for ns in $(kubectl get ns -o jsonpath='{.items[*].metadata.name}'); do                                                    
  for kind in deploy daemonset statefulset; do
    kubectl get "${kind}" -n "${ns}" -o name | xargs -I {} kubectl rollout restart {} -n "${ns}"
  done
done