Continental Innovates with Rancher and Kubernetes
In clusters where:
The Istio Ingress Gateway pod won’t be able to redirect ingress traffic to the workloads by default. This is because all the namespaces will be inaccessible from the namespace where Istio is installed. You have two options.
The first option is to add a new Network Policy in each of the namespaces where you intend to have ingress controlled by Istio. Your policy should include the following lines:
The second option is to move the istio-system namespace to the system project, which by default is excluded from the network isolation.