Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Menyelesaikan masalah konfigurasi
Bagian ini menjelaskan masalah umum Cloud Service Mesh dan cara mengatasinya.
Jika Anda memerlukan bantuan tambahan, lihat Mendapatkan dukungan.
Memeriksa MembershipState
Anda dapat memeriksa status terbaru mesh kapan saja dengan menjalankan perintah berikut:
gcloud container fleet mesh describe
Outputnya mirip dengan:
...
membershipSpecs:
projects/project_id/locations/global/memberships/cluster:
mesh:
management: MANAGEMENT_AUTOMATIC
membershipStates:
projects/project_id/locations/global/memberships/cluster:
servicemesh:
...
conditions:
- code: CONFIG_VALIDATION_WARNING
documentationLink: https://cloud.google.com/...
details: Application of one or more configs has failed. Error details are shown on individual config resources. See documentation link for more detail.
severity: WARNING
...
Kode Error MembershipState
Jika Cloud Service Mesh melaporkan kondisi ke MembershipState untuk cluster, hal ini dapat berarti konfigurasi Mesh (seperti Resource Khusus Istio) tidak dapat diterapkan. Deskripsi kode error berikut memberikan informasi selengkapnya tentang cara mengatasinya.
Kode Error
Penyebab
Resolusi
CONFIG_APPLY_INTERNAL_ERROR
Satu atau beberapa konfigurasi gagal diterapkan karena error internal.
Harap hubungi dukungan pelanggan.
QUOTA_EXCEEDED_*
Satu atau beberapa konfigurasi gagal diterapkan karena resource mencapai batas kuota.
Lihat Kuota untuk mengetahui informasi tentang kuota tertentu dan cara menaikkannya.
CONFIG_VALIDATION_ERROR
Satu atau beberapa konfigurasi gagal diterapkan karena konfigurasi tidak valid.
Error tertentu ditulis ke konfigurasi yang menyebabkannya. Informasi selengkapnya tentang cara mendiagnosisnya dijelaskan di bagian: Error Validasi Konfigurasi.
CONFIG_VALIDATION_WARNING
Kami menemukan potensi masalah di satu atau beberapa konfigurasi. Hal ini mungkin belum diterapkan, dan jika telah diterapkan, mungkin ada perilaku yang tidak diinginkan.
Kode CONFIG_VALIDATION_WARNING dan CONFIG_VALIDATION_ERROR menunjukkan bahwa masalah ditemukan pada konfigurasi mesh (Resource Kustom Istio atau Kubernetes) dan bahwa sebagian konfigurasi mungkin tidak diterapkan dengan benar.
Banyak detail error per resource yang ditulis ke resource yang berlaku. Perintah berikut dapat digunakan untuk menemukan konfigurasi yang tidak valid dan melihat pesan error tertentu. (Catatan: ini khusus untuk resource Istio, dan tidak semua error validasi dapat ditampilkan di sini).
{"name":"demo-envoy-filter","namespace":"default","kind":"EnvoyFilter","conditions":[{"lastTransitionTime":"2024-04-04T21:10:18.046975988Z","message":"This API is not supported","reason":"Invalid","status":"False","type":"Accepted"}]}
[[["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-09-04 UTC."],[],[],null,["# Resolving configuration issues\n==============================\n\nThis section explains common Cloud Service Mesh problems and how to resolve them.\nIf you need additional assistance, see [Getting support](/service-mesh/v1.21/docs/getting-support).\n\nChecking MembershipState\n------------------------\n\nAt any time you can check the most recent status of the mesh by running the following command: \n\n gcloud container fleet mesh describe\n\nThe output is similar to: \n\n ...\n membershipSpecs:\n projects/project_id/locations/global/memberships/cluster:\n mesh:\n management: MANAGEMENT_AUTOMATIC\n membershipStates:\n projects/project_id/locations/global/memberships/cluster:\n servicemesh:\n ...\n conditions:\n - code: CONFIG_VALIDATION_WARNING\n documentationLink: https://cloud.google.com/...\n details: Application of one or more configs has failed. Error details are shown on individual config resources. See documentation link for more detail.\n severity: WARNING\n ...\n\n### MembershipState Error Codes\n\nIf Cloud Service Mesh reports conditions to the MembershipState for a cluster, it could mean Mesh configurations (such as Istio Custom Resources) were not able to be applied. The following error code descriptions give more information on how to address them.\n\nConfiguration Validation Errors\n-------------------------------\n\n`CONFIG_VALIDATION_WARNING ` and ` CONFIG_VALIDATION_ERROR ` codes indicate problems were found on mesh configs (Istio or Kubernetes Custom Resources) and that a subset of configs may not have been properly applied.\n\nMany per-resource error details are written to the applicable resource. The following command can be used to locate the invalid configs and view the specific error messages. (Note: these are specifically for Istio resources, and not all validation errors may be displayed here). \n\n for resource in serviceentries destinationrules virtualservices gateways peerauthentications authorizationpolicies requestauthentications sidecars telemetries envoyfilters;\n do kubectl get $resource --all-namespaces --output=json | \\\n jq '.items[] | select(.status.conditions != null and any(.status.conditions[]; .type == \"Accepted\" and .status == \"False\")) | {\"name\": .metadata.name, \"namespace\": .metadata.namespace, \"kind\": .kind, \"conditions\": .status.conditions}';\n done\n\nThe output is similar to: \n\n {\n \"name\": \"demo-envoy-filter\",\n \"namespace\": \"default\",\n \"kind\": \"EnvoyFilter\",\n \"conditions\": [\n {\n \"lastTransitionTime\": \"2024-04-04T21:10:18.046975988Z\",\n \"message\": \"This API is not supported\",\n \"reason\": \"Invalid\",\n \"status\": \"False\",\n \"type\": \"Accepted\"\n }\n ]\n }"]]