2.18. Performance and scalability
The default ServiceMeshControlPlane settings are not intended for production use; they are designed to install successfully on a default OpenShift Container Platform installation, which is a resource-limited environment. After you have verified a successful SMCP installation, you should modify the settings defined within the SMCP to suit your environment.
2.18.1. Setting limits on compute resources 링크 복사링크가 클립보드에 복사되었습니다!
By default, spec.proxy has the settings cpu: 10m and memory: 128M. If you are using Pilot, spec.runtime.components.pilot has the same default values.
The settings in the following example are based on 1,000 services and 1,000 requests per second. You can change the values for cpu and memory in the ServiceMeshControlPlane.
Procedure
-
In the OpenShift Container Platform web console, click Operators
Installed Operators. - Click the Project menu and select the project where you installed the Service Mesh control plane, for example istio-system.
-
Click the Red Hat OpenShift Service Mesh Operator. In the Istio Service Mesh Control Plane column, click the name of your
ServiceMeshControlPlane, for examplebasic. Add the name of your standalone Jaeger instance to the
ServiceMeshControlPlane.- Click the YAML tab.
Set the values for
spec.proxy.runtime.container.resources.requests.cpu,spec.proxy.runtime.container.resources.requests.memory,components.kiali.container, andcomponents.global.oauthproxyin yourServiceMeshControlPlaneresource.Example version 2.6 ServiceMeshControlPlane
apiVersion: maistra.io/v2 kind: ServiceMeshControlPlane metadata: name: basic namespace: istio-system spec: version: v2.6 proxy: runtime: container: resources: requests: cpu: 600m memory: 50Mi limits: {} runtime: components: pilot: container: resources: requests: cpu: 1000m memory: 1.6Gi limits: {} kiali: container: resources: limits: cpu: "90m" memory: "245Mi" requests: cpu: "30m" memory: "108Mi" global.oauthproxy: container: resources: requests: cpu: "101m" memory: "256Mi" limits: cpu: "201m" memory: "512Mi"- To set values for Red Hat OpenShift Distributed Tracing Platform (Jaeger), see "Configuring and deploying the distributed tracing platform Jaeger".
- Click Save.
Verification
-
Click Reload to verify that the
ServiceMeshControlPlaneresource was configured correctly.