If you have restrictive Pod Security Policies enabled, then Istio may not be able to function correctly, because it needs certain permissions in order to install itself and manage pod infrastructure. In this section, we will configure a cluster with PSPs enabled for an Istio install, and also set up the Istio CNI plugin.
The Istio CNI plugin removes the need for each application pod to have a privileged
NET_ADMIN container. For further information, see the Istio CNI Plugin docs. Please note that the Istio CNI Plugin is in alpha.
- The cluster must be an RKE Kubernetes cluster.
- The cluster must have been created with a default PodSecurityPolicy.
To enable pod security policy support when creating a Kubernetes cluster in the Rancher UI, go to Advanced Options. In the Pod Security Policy Support section, click Enabled. Then select a default pod security policy.
1. Set the PodSecurityPolicy to unrestricted
An unrestricted PSP allows Istio to be installed.
Set the PSP to
unrestricted in the project where is Istio is installed, or the project where you plan to install Istio.
- Click ☰ > Cluster Management.
- Go to the cluster that you created and click Explore.
- Click Cluster > Projects/Namespaces.
- Find the Project: System and select the ⋮ > Edit Config.
- Change the Pod Security Policy option to be unrestricted, then click Save.
2. Enable the CNI
When installing or upgrading Istio through Apps & Marketplace (Rancher before v2.6.5) or Apps (Rancher v2.6.5+)
- Click Components.
- Check the box next to Enabled CNI.
- Finish installing or upgrading Istio.
The CNI can also be enabled by editing the
Istio should install successfully with the CNI enabled in the cluster.
3. Verify that the CNI is working
Verify that the CNI is working by deploying a sample application or deploying one of your own applications.