diff --git a/content/rancher/v2.5/en/istio/resources/_index.md b/content/rancher/v2.5/en/istio/resources/_index.md index fba30f972b7..d4fbc4f3777 100644 --- a/content/rancher/v2.5/en/istio/resources/_index.md +++ b/content/rancher/v2.5/en/istio/resources/_index.md @@ -20,14 +20,32 @@ The table below shows a summary of the minimum recommended resource requests and 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.](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) -Workload | CPU - Request | Mem - Request | CPU - Limit | Mem - Limit | Configurable +{{% tabs %}} +{{% tab "v2.5.6+" %}} + +| Workload | CPU - Request | Memory - Request | CPU - Limit | Memory - Limit | +|----------------------|---------------|------------|-----------------|-------------------| +| ingress gateway | 100m | 128mi | 2000m | 1024mi | +| egress gateway | 100m | 128mi | 2000m | 1024mi | +| istiod | 500m | 2048mi | No limit | No limit | +| proxy | 10m | 10mi | 2000m | 1024mi | +| **Totals:** | **710m** | **2314Mi** | **6000m** | **3072Mi** | + +{{% /tab %}} +{{% tab "v2.5.0-v2.5.5" %}} + +Workload | CPU - Request | Memory - Request | CPU - Limit | Mem - Limit | Configurable ---------:|---------------:|---------------:|-------------:|-------------:|-------------: -Istiod | 610m | 2186Mi | 4000m | 2048Mi | Y | Y -Istio-policy | 1000m | 1024Mi | 4800m | 4096Mi | Y -Istio-telemetry | 1000m | 10214Mi | 4800m | 4096Mi | Y -Istio-ingressgateway | 2000m | 1024Mi | 10m | 40Mi | Y -Others | 500m | 500Mi | - | - | Y -**Total** | **4500m** | **5620Mi** | **>12300m** | **>14848Mi** | **-** +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 | - + +{{% /tab %}} +{{% /tabs %}} + + # Configuring Resource Allocations @@ -41,8 +59,23 @@ You can find more information about Istio configuration in the [official Istio d To configure the resources allocated to an Istio component, 1. In the Rancher **Cluster Explorer**, navigate to your Istio installation in **Apps & Marketplace** -1. Click **Upgrade** to edit the base components via changes the values.yaml or add an [overlay file]({{}}/rancher/v2.5/en/istio/v2.5/configuration-reference/#overlay-file). +1. Click **Upgrade** to edit the base components via changes the values.yaml or add an [overlay file]({{}}/rancher/v2.5/en/istio/v2.5/configuration-reference/#overlay-file). For more information about editing the overlay file, see [this section.](./#editing-the-overlay-file) 1. Change the CPU or memory allocations, the nodes where each component will be scheduled to, or the node tolerations. 1. Click **Upgrade.** to rollout changes -**Result:** The resource allocations for the Istio components are updated. \ No newline at end of file +**Result:** The resource allocations for the Istio components are updated. + +### Editing the Overlay File + +The overlay file can contain any of the values in the [Istio Operator spec.](https://istio.io/latest/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec) The overlay file included with the Istio application is just one example of a potential configuration of the overlay file. + +As long as the file contains `kind: IstioOperator` and the YAML options are valid, the file can be used as an overlay. + +In the example overlay file provided with the Istio application, the following section allows you to change Kubernetes resources: + +``` +# k8s: +# resources: +# requests: +# cpu: 200m +``` \ No newline at end of file diff --git a/content/rancher/v2.x/en/istio/v2.5/resources/_index.md b/content/rancher/v2.x/en/istio/v2.5/resources/_index.md index 19dde46e0d2..1f82cfcaa10 100644 --- a/content/rancher/v2.x/en/istio/v2.5/resources/_index.md +++ b/content/rancher/v2.x/en/istio/v2.5/resources/_index.md @@ -7,7 +7,7 @@ aliases: - /rancher/v2.x/en/cluster-admin/tools/istio/resources - /rancher/v2.x/en/istio/resources --- -_This section applies to Istio in Rancher v2.5.0. If you are using Rancher v2.4.x, refer to [this section.]({{}}/rancher/v2.x/en/cluster-admin/tools/istio/)_ +_This section applies to Istio in Rancher v2.5.x. If you are using Rancher v2.4.x, refer to [this section.]({{}}/rancher/v2.x/en/cluster-admin/tools/istio/)_ This section describes the minimum recommended computing resources for the Istio components in a cluster. @@ -21,14 +21,32 @@ The table below shows a summary of the minimum recommended resource requests and 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.](https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/) -Workload | CPU - Request | Mem - Request | CPU - Limit | Mem - Limit | Configurable +{{% tabs %}} +{{% tab "v2.5.6+" %}} + +| Workload | CPU - Request | Memory - Request | CPU - Limit | Memory - Limit | +|----------------------|---------------|------------|-----------------|-------------------| +| ingress gateway | 100m | 128mi | 2000m | 1024mi | +| egress gateway | 100m | 128mi | 2000m | 1024mi | +| istiod | 500m | 2048mi | No limit | No limit | +| proxy | 10m | 10mi | 2000m | 1024mi | +| **Totals:** | **710m** | **2314Mi** | **6000m** | **3072Mi** | + +{{% /tab %}} +{{% tab "v2.5.0-v2.5.5" %}} + +Workload | CPU - Request | Memory - Request | CPU - Limit | Mem - Limit | Configurable ---------:|---------------:|---------------:|-------------:|-------------:|-------------: -Istiod | 610m | 2186Mi | 4000m | 2048Mi | Y | Y -Istio-policy | 1000m | 1024Mi | 4800m | 4096Mi | Y -Istio-telemetry | 1000m | 10214Mi | 4800m | 4096Mi | Y -Istio-ingressgateway | 2000m | 1024Mi | 10m | 40Mi | Y -Others | 500m | 500Mi | - | - | Y -**Total** | **4500m** | **5620Mi** | **>12300m** | **>14848Mi** | **-** +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 | - + +{{% /tab %}} +{{% /tabs %}} + + # Configuring Resource Allocations @@ -42,8 +60,24 @@ You can find more information about Istio configuration in the [official Istio d To configure the resources allocated to an Istio component, 1. In the Rancher **Cluster Explorer**, navigate to your Istio installation in **Apps & Marketplace** -1. Click **Upgrade** to edit the base components via changes the values.yaml or add an [overlay file]({{}}/rancher/v2.x/en/istio/v2.5/configuration-reference/#overlay-file). +1. Click **Upgrade** to edit the base components via changes the values.yaml or add an [overlay file]({{}}/rancher/v2.x/en/istio/v2.5/configuration-reference/#overlay-file). For more information about editing the overlay file, see [this section.](./#editing-the-overlay-file) 1. Change the CPU or memory allocations, the nodes where each component will be scheduled to, or the node tolerations. 1. Click **Upgrade.** to rollout changes -**Result:** The resource allocations for the Istio components are updated. \ No newline at end of file +**Result:** The resource allocations for the Istio components are updated. + + +### Editing the Overlay File + +The overlay file can contain any of the values in the [Istio Operator spec.](https://istio.io/latest/docs/reference/config/istio.operator.v1alpha1/#IstioOperatorSpec) The overlay file included with the Istio application is just one example of a potential configuration of the overlay file. + +As long as the file contains `kind: IstioOperator` and the YAML options are valid, the file can be used as an overlay. + +In the example overlay file provided with the Istio application, the following section allows you to change Kubernetes resources: + +``` +# k8s: +# resources: +# requests: +# cpu: 200m +``` \ No newline at end of file