Cloud Service Mesh dan Traffic Director kini bergabung menjadi Cloud Service Mesh. Untuk mengetahui informasi selengkapnya, lihat ringkasan Cloud Service Mesh.
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menyelesaikan masalah proxy sidecar di Cloud Service Mesh
Bagian ini menjelaskan masalah proxy sidecar Cloud Service Mesh yang umum dan cara menyelesaikannya.
Jika Anda memerlukan bantuan tambahan, lihat Mendapatkan dukungan.
Penampung istio-proxy dihentikan karena peristiwa OOM
Di bagian ini, kita mengasumsikan bahwa penampung istio-proxy tidak dihentikan oleh
peristiwa SystemOOM, dan node kubernetes tidak dalam kondisi MemoryPressure.
Penampung sidecar istio-proxy memiliki batas resource secara default.
Jika penampung istio-proxy dihentikan dengan Reason: OOMKilled, Anda perlu memahami mengapa Envoy menggunakan memori.
Jika Anda mengalami pemadaman produksi, solusi cepatnya adalah menaikkan batas untuk semua penampung menggunakan IstioOperator:
Jika mengalami masalah ini dengan workload tertentu, Anda dapat mengubah batas
hanya pada workload tersebut dengan menambahkan
anotasi berikut.
sidecar.istio.io/proxyMemory
sidecar.istio.io/proxyMemoryLimit
Pastikan Anda tidak memiliki batas yang lebih rendah dari nilai default.
Solusi jangka panjangnya adalah mengurangi jejak memori penampung sidecar istio-proxy
Anda. Secara default, semua proxy sidecar diprogram dengan konfigurasi yang diperlukan untuk menjangkau instance workload lainnya di mesh.
Istio menyediakan definisi resource kustom Sidecar
untuk membatasi jumlah endpoint yang diprogram ke proxy sidecar, sehingga
mengurangi konsumsi memori penampung istio-proxy.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[],[],null,["# Resolving sidecar proxies issues in Cloud Service Mesh\n======================================================\n\nThis section explains common Cloud Service Mesh sidecar proxies problems and how to\nresolve them.\nIf you need additional assistance, see [Getting support](/service-mesh/docs/getting-support).\n\nThe `istio-proxy` container is killed because of a OOM event\n------------------------------------------------------------\n\nIn this section we assume that the `istio-proxy` container is not killed by a\n`SystemOOM` event, and the kubernetes node is not in `MemoryPressure` condition.\nThe `istio-proxy` sidecar container has by default [resource limits](https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits).\nIf the istio-proxy container gets killed with `Reason: OOMKilled` it is necessary\nto understand why Envoy is consuming the memory.\n\nIf you are facing a production outage, a quick workaround is to raise the limits\nfor all containers using `IstioOperator`: \n\n ---\n apiVersion: install.istio.io/v1alpha1\n kind: IstioOperator\n spec:\n values:\n global:\n proxy:\n resources:\n requests:\n memory: 128Mi\n limits:\n memory: 1Gi\n\nIf you are facing this issue with specific workloads, you can change the limit\njust on those workloads by adding the following\n[annotations](https://istio.io/v1.26/docs/reference/config/annotations/).\n\n- `sidecar.istio.io/proxyMemory`\n- `sidecar.istio.io/proxyMemoryLimit`\n\nPlease make sure you don't have limits that are lower of the default values.\n| **Note:** because this container is injected at the Pod creation, this setting will be effective only for newly created Pods.\n\nThe long term solution is to reduce the memory footprint of your `istio-proxy`\nsidecar containers. By default all sidecar proxies are programmed with the\nnecessary configuration to reach any other workload instance in the mesh.\nIstio provides the [custom resource definition `Sidecar`](https://istio.io/v1.26/docs/reference/config/networking/sidecar/)\nto limit the number of endpoints programmed to sidecar proxies, and therefore\nreduce the memory consumption of the `istio-proxy` container."]]
