The CPU and memory allocations for each component are
Before enabling Istio, we recommend that you confirm that your Rancher worker nodes have enough CPU and memory to run all of the components of Istio.
In Kubernetes, the resource request indicates that the workload will not deployed on a node unless the node has at least the specified amount of memory and CPU available. If the workload surpasses the limit for CPU or memory, it can be terminated or evicted from the node. For more information on managing resource limits for containers, refer to the Kubernetes documentation.
Workload | CPU - Request | Memory - Request | CPU - Limit | Mem - Limit | Configurable |
---|---|---|---|---|---|
Istiod | 500m | 2048Mi | No limit | No limit | Y |
Istio-Mixer | 1000m | 1000Mi | 4800m | 4000Mi | Y |
Istio-ingressgateway | 100m | 128Mi | 2000m | 1024Mi | Y |
Others | 10m | - | - | - | Y |
Totals: | 1710m | 3304Mi | >8800m | >6048Mi | - |
Configuring Resource Allocations
You can individually configure the resource allocation for each type of Istio component. This section includes the default resource allocations for each component.
To make it easier to schedule the workloads to a node, a cluster-admin can reduce the CPU and memory resource requests for the component. However, the default CPU and memory allocations are the minimum that we recommend.
To configure the resources allocated to an Istio component,
- Click Upgrade to edit the base components via changes to the values.yaml or add an overlay file. For more information about editing the overlay file, see
- Click Upgrade. to rollout changes
Result: The resource allocations for the Istio components are updated.
The overlay file can contain any of the values in the Istio Operator spec. The overlay file included with the Istio application is just one example of a potential configuration of the overlay file.
In the example overlay file provided with the Istio application, the following section allows you to change Kubernetes resources: