Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Memantau resource
Untuk mendapatkan informasi tentang resource, Anda dapat menggunakan kubectl.
Sebelum memulai
Untuk menyelesaikan langkah-langkah ini, Anda memerlukan resource Config Connector yang ada.
Untuk contoh resource, lihat
Memulai Config Connector.
Mencantumkan semua resource
Anda dapat membuat daftar resource yang dikelola Config Connector dengan menjalankan perintah berikut:
kubectl get gcp
Menentukan status resource
Anda dapat menentukan apakah resource Anda sudah siap dengan melihat
status.condition.
Config Connector memperbarui status untuk mencerminkan status resource Anda saat ini.
kubectl wait --for=condition=READY KINDNAME
Ganti kode berikut:
KIND: jenis resource Anda. Contoh, PubSubTopic.
NAME: nama resource Anda
Melihat peristiwa
Config Connector membuat peristiwa Kubernetes dengan informasi dan error tentang
pengelolaan resource. Anda dapat melihat peristiwa untuk resource tertentu, atau semua peristiwa di lingkungan Config Connector.
Melihat peristiwa untuk satu resource
Anda dapat melihat peristiwa untuk satu resource dengan memeriksa kolom Events
dalam output perintah berikut:
kubectl describe KINDNAME
Ganti kode berikut:
KIND: jenis resource Anda
NAME: nama resource Anda
Misalnya, jika Anda memiliki resource SQLInstance Config Connector
bernama sqlinstance-sample, gunakan perintah berikut untuk melihat peristiwanya:
kubectl describe sqlinstance sqlinstance-sample
Melihat peristiwa untuk namespace
Untuk melihat peristiwa untuk semua resource Kubernetes di namespace tertentu, termasuk
resource Config Connector Anda, jalankan perintah berikut:
kubectl --namespace CC_NAMESPACE get events
Ganti CC_NAMESPACE dengan namespace tempat Konektor Konfigurasi mengelola resource.
Peristiwa khusus Konektor Konfigurasi
Config Connector dapat membuat jenis peristiwa berikut:
Memperbarui
Terjadi saat resource dasar Google Cloudresource Config Connector sedang diperbarui.
UpToDate
Terjadi saat rekonsiliasi resource Konektor Konfigurasi berhasil.
Jenis peristiwa ini berarti bahwa resource Google Cloud yang mendasarinya kini
cocok dengan status yang diinginkan yang ditentukan oleh resource Config Connector.
UpdateFailed
Terjadi saat rekonsiliasi resource Konektor Konfigurasi gagal.
DependencyNotReady
Terjadi saat resource Config Connector yang direferensikan belum siap. Anda dapat
menentukan apakah resource siap dengan memeriksa
statusnya.
DependencyNotFound
Terjadi saat resource Config Connector yang direferensikan atau Secret Kubernetes
tidak ditemukan.
DependencyInvalid
Terjadi saat referensi tidak valid. Misalnya, resource Config Connector yang mereferensikan Secret Kubernetes. Jika Secret ada, tetapi jika secret tersebut tidak berisi kunci yang direferensikan, referensi tersebut dianggap tidak valid.
Menghapus
Terjadi saat resource Config Connector dihapus dari Server Kubernetes API.
Deleted
Terjadi saat resource Config Connector berhasil dihapus dari
Server Kubernetes API.
DeleteFailed
Terjadi saat resource Config Connector gagal dihapus dari
Server Kubernetes API.
ManagementConflict
Terjadi saat resource Konektor Konfigurasi gagal mengambil kepemilikan resource Google Cloud yang mendasarinya. Jika hal ini terjadi, biasanya karena resource Config Connector lain sudah memiliki kepemilikan resourceGoogle Cloud . Baca selengkapnya tentang cara Config Connector menangani
konflik antar-resource Config Connector.
PreActuationTransformFailed
Terjadi saat resource Config Connector gagal melakukan transformasi pra-aktuasi.
Jenis peristiwa ini kemungkinan berarti bahwa konfigurasi resource tidak valid.
PostActuationTransformFailed
Terjadi saat resource Config Connector gagal melakukan transformasi pasca-aktuasi.
Tidak dikelola
Terjadi saat Config Connector berada dalam
mode dengan namespace
dan resource Config Connector berada dalam namespace tempat Config Connector
tidak diaktifkan (yaitu, namespace tidak memiliki
objek ConfigConnectorContext).
Peristiwa ini dapat terjadi meskipun namespace memiliki
ConfigConnectorContext jika ConfigConnectorContext dibuat pada
waktu yang sama dengan resource Config Connector. Anda hanya perlu menunggu
beberapa saat agar Config Connector mulai mengelola resource.
[[["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-11 UTC."],[[["\u003cp\u003eYou can use \u003ccode\u003ekubectl\u003c/code\u003e commands to monitor resources managed by Config Connector, including listing them with \u003ccode\u003ekubectl get gcp\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe status of a resource can be determined by examining its \u003ccode\u003estatus.condition\u003c/code\u003e and you can use \u003ccode\u003ekubectl wait --for=condition=READY\u003c/code\u003e to wait for a resource to become ready.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector generates Kubernetes events that you can view for a specific resource using \u003ccode\u003ekubectl describe KIND NAME\u003c/code\u003e, or for all resources in a namespace with \u003ccode\u003ekubectl --namespace CC_NAMESPACE get events\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector events, like \u003ccode\u003eUpdating\u003c/code\u003e, \u003ccode\u003eUpToDate\u003c/code\u003e, \u003ccode\u003eUpdateFailed\u003c/code\u003e, \u003ccode\u003eDependencyNotReady\u003c/code\u003e, and others, provide information about the lifecycle and state of resources.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector events, such as \u003ccode\u003eManagementConflict\u003c/code\u003e, \u003ccode\u003ePreActuationTransformFailed\u003c/code\u003e, \u003ccode\u003ePostActuationTransformFailed\u003c/code\u003e, and \u003ccode\u003eUnmanaged\u003c/code\u003e give specific data regarding certain issues with the resources.\u003c/p\u003e\n"]]],[],null,["# Monitoring your resources\n=========================\n\n*** ** * ** ***\n\nTo get information on your resources, you can use `kubectl`.\n\nBefore you begin\n----------------\n\nTo complete these steps, you need existing Config Connector resources.\nFor an example resource, see\n[Getting started with Config Connector](/config-connector/docs/how-to/getting-started).\n\nListing all resources\n---------------------\n\nYou can list the resources that Config Connector manages with, by running\nthe following command: \n\n```\nkubectl get gcp\n```\n\nDetermining a resource's status\n-------------------------------\n\nYou can determine if your resource is ready by looking at its\n[status.condition](/config-connector/docs/concepts/resources#status_condition).\nConfig Connector updates the status to reflect the current state of\nyour resource. \n\n```\nkubectl wait --for=condition=READY KIND NAME\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eKIND\u003c/var\u003e: your resource's kind. For example, `PubSubTopic`.\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: your resource's name\n\nViewing events\n--------------\n\nConfig Connector creates Kubernetes events with information and errors about\nmanaging resources. You can view events for a specific resource, or all events\nin your Config Connector environment.\n\n### Viewing events for a single resource\n\nYou can view the events for a single resource by examining the `Events` field\nin the output of the following command: \n\n```\nkubectl describe KIND NAME\n```\n\nReplace the following:\n\n- \u003cvar translate=\"no\"\u003eKIND\u003c/var\u003e: your resource's kind\n- \u003cvar translate=\"no\"\u003eNAME\u003c/var\u003e: your resource's name\n\nFor example, if you had a Config Connector `SQLInstance` resource\nnamed `sqlinstance-sample`, use the following command to view its events: \n\n```\nkubectl describe sqlinstance sqlinstance-sample\n```\n\n### Viewing events for a namespace\n\nTo see the events for all Kubernetes resources in a given namespace, including\nyour Config Connector resources, run the following command: \n\n```\nkubectl --namespace CC_NAMESPACE get events\n```\n\nReplace \u003cvar translate=\"no\"\u003eCC_NAMESPACE\u003c/var\u003e with the namespace Config Connector\nmanages resources from.\n\n### Config Connector-specific events\n\nConfig Connector can create the following event types:\n\nUpdating\n: Occurs when a Config Connector resource's underlying Google Cloud\n resource is being updated.\n\nUpToDate\n: Occurs when a Config Connector resource's reconciliation has succeeded.\n This event type means that the underlying Google Cloud resource now\n matches the desired state specified by the Config Connector resource.\n\nUpdateFailed\n: Occurs when a Config Connector resource's reconciliation has failed.\n\nDependencyNotReady\n: Occurs when a referenced Config Connector resource is not ready. You can\n determine whether a resource is ready by [checking its\n status](#determining-resource-status).\n\nDependencyNotFound\n: Occurs when a referenced Config Connector resource or Kubernetes Secret\n is not found.\n\nDependencyInvalid\n: Occurs when a reference is invalid. For example, suppose a Config Connector\n resource that references a Kubernetes Secret. If the Secret exists, but if\n it does not contain the key that is being referenced, then the reference\n is said to be invalid.\n\nDeleting\n: Occurs when Config Connector resource is being deleted from the Kubernetes\n API Server.\n\nDeleted\n: Occurs when a Config Connector resource has successfully been deleted from\n the Kubernetes API Server.\n\nDeleteFailed\n: Occurs when a Config Connector resource has failed to be deleted from the\n Kubernetes API Server.\n\nManagementConflict\n: Occurs when a Config Connector resource fails to take ownership of the\n underlying Google Cloud resource. When this occurs, it is usually\n because another Config Connector resource already has ownership of the\n Google Cloud resource. Read more about [how Config Connector handles\n conflicts between multiple Config Connector resources](/config-connector/docs/concepts/managing-conflicts).\n\nPreActuationTransformFailed\n: Occurs when a Config Connector resource fails to perform pre-actuation transformations.\n This event type likely means that the resource configuration is invalid.\n\nPostActuationTransformFailed\n: Occurs when a Config Connector resource fails to perform post-actuation transformations.\n\nUnmanaged\n\n: Occurs when Config Connector is in\n [namespaced-mode](/config-connector/docs/how-to/install-namespaced)\n and the Config Connector resource is in a namespace where Config Connector\n is not enabled (that is, the namespace does not have a\n `ConfigConnectorContext` object).\n\n This event can occur even if the namespace does have a\n `ConfigConnectorContext` if the `ConfigConnectorContext` was created around\n the same time as the Config Connector resource. You just need to wait\n some time for Config Connector to start managing the resource.\n\nWhat's next\n-----------\n\n- Learn more about\n [Kubernetes application introspection](https://kubernetes.io/docs/tasks/debug-application-cluster/debug-application-introspection/).\n\n- Monitor your Config Connector installation with\n [Prometheus](/config-connector/docs/how-to/monitoring-prometheus)."]]
