Istiod는 수직(대규모 요청)과 수평(여러 개의 복제본)으로 원활하게 확장됩니다. CPU 한도가 지나치게 제한적이지 않은지 확인합니다. Istiod가 CPU 한도에 도달하면 제한이 발생할 수 있으며, 이는 구성 배포에 부정적인 영향을 미칩니다. 성능 문제가 발생하는 경우 각 버전에 성능 최적화 기능이 있으므로 최신 버전의 Cloud Service Mesh로 업그레이드하는 것이 좋습니다.
클러스터 크기가 크게 변경되면 수명이 긴 연결로 인해 일시적으로 불균형 부하가 발생할 수 있습니다. 이렇게 되면 최대 연결 수명이 30분까지 단축되어 Envoy에 gRPC config stream
closed: 13과 같은 오류 메시지가 반환될 수 있으며, 이로 인해 부하가 원활하게 다시 분산됩니다.
Istiod의 복제본을 여러 개(기본값: 2개) 만들거나 극단적인 클러스터 수직 확장이 예상되는 경우 사전 확장을 수행하여 이 문제를 완화합니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["Resolving scaling issues in Cloud Service Mesh **Note:** This guide only supports Cloud Service Mesh with Istio APIs and does not support Google Cloud APIs. For more information see, [Cloud Service Mesh overview](/service-mesh/docs/overview).\n\nThis section explains common Cloud Service Mesh problems and how to resolve\nthem. If you need additional assistance, see\n[Getting support](/service-mesh/docs/getting-support).\n\nScaling factors\n\n[Istiod](https://istio.io/v1.26/blog/2020/istiod/)\nsends configuration to each sidecar using a long-lived gRPC stream. It has\nseveral characteristics that affect scaling:\n\n- The size of the configuration to generate:\n - Total number of services/pods \\& Istio resources\n - For large scale, adjust settings for the [Sidecar](https://istio.io/v1.26/docs/reference/config/networking/sidecar/) to reduce the configuration size.\n- The rate of change in the environment:\n - When a new service is created or the Istio configuration is changed, full updates are sent to proxies.\n - Adding new endpoints is inexpensive for performance, because only incremental updates are sent.\n- The number of proxies for which configuration is generated:\n - Affected by the number of gateways and pods with a sidecar.\n\nScaling considerations\n\nIstiod scales well vertically (large requests) and horizontally (more\nreplicas). Ensure that your CPU limits are not too restrictive; if Istiod\nreaches the CPU limit, throttling may occur which will negatively affect\nconfiguration distribution. If you encounter performance issues, consider\nupgrading to the latest version of Cloud Service Mesh, as each version has\nperformance optimizations.\n\nFor more guidance on scaling your mesh, see the\n[Scalability best practices guide](/service-mesh/docs/operate-and-maintain/scalability-best-practices).\n\nUnbalanced load\n\nLarge changes in cluster size might cause a temporarily unbalanced load, due to\nthe long-lived connections. This is mitigated by a 30 minute maximum connection\nage, which might result in error messages in Envoy, such as `gRPC config stream\nclosed: 13`, which allows the load to naturally rebalance.\n\nMitigate this issue by having multiple replicas of Istiod (the default is 2\nreplicas), and pre-scaling if you expect extreme cluster scale-ups."]]
