Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Mendiagnosis masalah cluster
Fitur health check secara rutin memantau kondisi bidang kontrol cluster dan beberapa komponen penting, serta membantu Anda mendeteksi dan mendiagnosis potensi masalah pada cluster.
Pemeriksa kondisi cluster mendeteksi dan memberi tahu Anda tentang masalah berikut dalam cluster:
Kesehatan kube-scheduler pada node bidang kontrol: Jika kube-scheduler tidak sehat, hal ini menunjukkan bahwa cluster mengalami masalah dalam menetapkan Pod ke node. Untuk menyelidiki lebih lanjut, Anda dapat memeriksa log kube-scheduler Pod
log.
Kondisi kube-controller-manager pada node bidang kontrol: kube-controller-manager memantau berbagai pengontrol, seperti pengontrol ReplicaSet, Deployment, dan Namespace, serta pengontrol lainnya. Jika kube-controller-manager dianggap tidak sehat, hal ini menunjukkan bahwa satu atau beberapa pengontrol yang dikelolanya mungkin tidak berfungsi dengan baik. Untuk menentukan masalah yang tepat, Anda dapat memeriksa log Pod kube-controller-manager, yang mungkin memberikan informasi lebih lanjut tentang pengontrol yang tidak berfungsi.
Kapasitas volume root: Pemeriksa kondisi memeriksa kapasitas yang memadai
pada volume root setiap node bidang kontrol. Jika kapasitas yang tersedia
berada di bawah 512 MB, pemeriksa kondisi akan memberi tahu Anda tentang potensi risiko
kehabisan ruang disk.
Melihat peristiwa health check
Untuk melihat pemberitahuan dari pemeriksa kondisi untuk cluster tertentu, jalankan perintah berikut:
GOOGLE_CLOUD_LOCATION: nama lokasi Google Cloud
yang mengelola cluster
Berikut kutipan jenis output yang akan Anda dapatkan:
{
"name": "some-cluster-name",
"description": "test-cluster",
...
"errors": [
{
"message": "Replica (replica-name)": kube-controller-manager is unhealthy"
},
{
"message": "Replica (replica-name)": not enough disk space on root volume, only 9 MB left"
}
]
...
}
Dalam contoh ini, pesan error menunjukkan bahwa komponen kube-controller-manager tidak berfungsi dengan baik, dan kapasitas pada volume root node bidang kontrol semakin menipis.
[[["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-07-14 UTC."],[],[],null,["# Diagnose cluster issues\n=======================\n\nThe health check feature regularly monitors the health of the cluster control\nplane and several critical components, and helps you detect and diagnose\npotential problems with your clusters.\nIf you need additional assistance, reach out to [Cloud Customer Care](/kubernetes-engine/multi-cloud/docs/azure/getting-support).\n\nIssues detected\n---------------\n\nThe cluster health checker detects and alerts you to the\nfollowing issues in a cluster:\n\n- **`kube-scheduler` health on control plane nodes** : If the `kube-scheduler`\n is unhealthy, this suggests that the cluster is having trouble assigning Pods\n to nodes. To investigate further, you can examine the `kube-scheduler` Pod\n log.\n\n- **`kube-controller-manager` health on control plane nodes** : The\n `kube-controller-manager` monitors\n various controllers, such as the ReplicaSet, Deployment, and Namespace\n controllers, among others. If the `kube-controller-manager` is deemed\n unhealthy, this suggests that one or more of the controllers it manages might\n not be working properly. To determine the precise issue, you can examine the\n `kube-controller-manager` Pod log, which might provide more information about\n the malfunctioning controller(s).\n\n- **Root volume capacity**: The health checker checks for sufficient capacity\n on the root volume of each control plane node. If the available capacity\n falls under 512MB, the health checker alerts you to the potential risk of\n running out of disk space.\n\nView health check events\n------------------------\n\nTo view alerts from the health checker for a specific cluster, run the following\ncommand: \n\n gcloud container azure clusters describe \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e \\\n --location \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eCLUSTER_NAME\u003c/var\u003e: your cluster's name\n- \u003cvar translate=\"no\"\u003eGOOGLE_CLOUD_LOCATION\u003c/var\u003e: the name of the Google Cloud location that manages the cluster\n\nHere's an excerpt of the kind of output you can expect:\n\n```\n{\n \"name\": \"some-cluster-name\",\n \"description\": \"test-cluster\",\n ...\n \"errors\": [\n {\n \"message\": \"Replica (replica-name)\": kube-controller-manager is unhealthy\"\n },\n {\n \"message\": \"Replica (replica-name)\": not enough disk space on root volume, only 9 MB left\"\n }\n ]\n ...\n}\n```\n\nIn this example, the error message indicates that a `kube-controller-manager`\ncomponent is unhealthy, and that the capacity on a control plane node's root\nvolume is getting low.\n\nWhat's next\n-----------\n\nIf you need additional assistance, reach out to [Cloud Customer Care](/kubernetes-engine/multi-cloud/docs/azure/getting-support)."]]
