Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Resource
Config Connector menyertakan kumpulan
Custom Resource Definitions
(CRD). Setiap CRD memungkinkan Anda mengonfigurasi resource Google Clouddari Kubernetes. Config Connector juga memungkinkan Anda memanfaatkan sejumlah fitur Kubernetes untuk mengelola resource Google Cloud .
Halaman ini memperkenalkan cara Config Connector menggunakan objek Kubernetes dan metadatanya.
Objek Kubernetes dan resource Config Connector
Misalnya, saat Anda membuat
Objek Kuberneteskind: SQLInstance, Konektor Konfigurasi akan membuat Instance Cloud SQL.
Bagian ini menjelaskan cara Config Connector memperluas jenis objek.
Kolom spec berisi semua kolom yang menentukan status objek yang diinginkan, kecuali Labels. Subkolom spec
merujuk ke resource Google Cloud terkait. Saat Anda mengubah
subkolom, nilai resource Google Cloud
pada akhirnya akan konsisten dengan nilai yang Anda inginkan.
Contoh kolom yang dapat ditulis adalah databaseVersion dalam resource SQLInstance.
Status
Kolom status hanya dapat dibaca dan berisi status objek Anda saat ini.
Config Connector secara berkala membaca informasi tentang resource Google CloudAnda dan memperbarui status. Anda dapat memeriksa pesan error atau kesiapan resource dengan melihat Status.Condition.
Contoh kolom status hanya baca adalah connectionName dari resource SQLInstance.
Metadata objek
Setiap resource Config Connector menyertakan kolom metadata. Bagian ini menjelaskan cara Config Connector menggunakan subkolom dalam
metadata.
Nama
Nama resource Config Connector. Nama ini harus mengikuti
konvensi penamaan
nama objek Kubernetes. Nama ini digunakan secara default sebagai nama
resource Google Cloud yang sesuai. Jika kolom resourceID
didukung di resource Config Connector, Anda dapat menentukan nama
yang berbeda, yang mengikuti konvensi penamaan resource
Google Cloud, untuk resource Google Cloud yang sesuai di
kolom spec.resourceID. Untuk mengetahui informasi selengkapnya, lihat
Mengelola resource dengan kolom resourceID.
Namespace
Namespace tempat Anda membuat resource Config Connector menentukan project yang berisi resource Google Cloud . Untuk mengetahui informasi selengkapnya tentang
namespace, lihat
Namespace dan Google Cloud Project Kubernetes.
Label
Label di kolom metadata resource Config Connector juga ditambahkan
ke resource Google Cloud terkait.
Selain itu, Config Connector menambahkan label sistem bernama managed-by-cnrm
dengan nilai true ke Google Cloud resource Anda.
Anotasi
Konektor Konfigurasi dapat mengambil tindakan tambahan pada resource Anda yang
tidak ditentukan dalam spec. Tindakan ini ditentukan dalam subkolom
metadata.annotations. Nilai anotasi harus berupa string.
Jenis anotasi yang didukung Konektor Konfigurasi dijelaskan dalam anotasi.
Folder dan resource hierarkis
Selain mengelola resource di produk Google Cloud ,
Config Connector mendukung pembuatan dan pengelolaan resource dalam
Google Cloud Folder dan Organisasi.
Untuk informasi selengkapnya, lihat Namespace dan project.
Menggunakan RBAC untuk Kontrol Akses
Role Based Access Control (RBAC) Kubernetes mengamankan resource Anda. Anda dapat mengontrol pembuatan resource Google Clouddengan menetapkan izin RBAC. Untuk informasi selengkapnya, lihat
Mengamankan akses ke resource.
Kondisi Status
Config Connector menggunakan kondisi siap di
status.condition untuk dua tujuan:
yang menunjukkan kapan resource siap. Saat resource direkonsiliasi dan
siap, status.condition.status-nya akan ditetapkan ke True. Untuk memeriksa kapan resource siap, lihat Menunggu resource siap
menampilkan error atau informasi tambahan. Kondisi siap
memiliki kolom Message dan Reason yang memberikan informasi
tambahan tentang status resource.
Acara
Perubahan status penting untuk resource Config Connector terlihat sebagai peristiwa Kubernetes. Untuk informasi selengkapnya, lihat
Melihat peristiwa.
[[["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\u003eConfig Connector allows the configuration of Google Cloud resources using Kubernetes Custom Resource Definitions (CRDs), extending Kubernetes capabilities.\u003c/p\u003e\n"],["\u003cp\u003eEach Config Connector resource includes a \u003ccode\u003espec\u003c/code\u003e field, defining the desired state of the object, and a read-only \u003ccode\u003estatus\u003c/code\u003e field, reflecting the current state as observed in Google Cloud.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector resources utilize Kubernetes object metadata, including names, namespaces, and labels, with labels being mirrored to the associated Google Cloud resource.\u003c/p\u003e\n"],["\u003cp\u003eConfig Connector supports \u003ccode\u003emetadata.annotations\u003c/code\u003e, which allows users to define actions not within \u003ccode\u003espec\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eConfig connector displays error information and if the resource is ready through \u003ccode\u003estatus.condition\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Resources\n=========\n\n*** ** * ** ***\n\nConfig Connector includes a collection of\n[Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)\n(CRDs). Each CRD allows you to configure a Google Cloud\nresource from Kubernetes. Config Connector also allows you to leverage a number\nof Kubernetes features for managing Google Cloud resources.\n\nThis page introduces you to how Config Connector uses Kubernetes objects and\ntheir metadata.\n\nKubernetes objects and Config Connector resources\n-------------------------------------------------\n\nFor example, when you create a\n[Kubernetes Object](https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/)\nof `kind: SQLInstance`, Config Connector creates a Cloud SQL Instance.\nThis section describes how Config Connector extends object types.\n\n### Spec and Status\n\nEach Config Connector resource is a\n[Kubernetes object](https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/)\nwith a\n[`Spec` and a `Status`](https://kubernetes.io/docs/concepts/overview/working-with-objects/kubernetes-objects/#object-spec-and-status).\n\nSpec\n: The `spec` field contains all the fields that define an object's desired\n state, with the exception of [`Labels`](#labels). The subfields of a `spec`\n refer to the associated Google Cloud resource. When you change a\n subfield, the Google Cloud resource's value is\n [eventually consistent](#declarative_configuration_and_eventual_consistency) with your intended value.\n: An example of a writable field is `databaseVersion` in a SQLInstance\n resource.\n\nStatus\n: The `status` field is read-only and contains the current state of your object.\n Config Connector periodically reads information on your Google Cloud\n resource and updates the `status`. You can check a resource's error messages\n or readiness by looking at the [`Status.Condition`](#status_condition).\n: An example read-only `status` field is the `connectionName` of a\n SQLInstance resource.\n\nObject metadata\n---------------\n\nEach Config Connector resource includes a\n[metadata](https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/#attaching-metadata-to-objects)\nfield. This section describes how Config Connector uses subfields within\nmetadata.\n\nName\n: The name of a Config Connector resource. It should follow the\n [naming convention](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-subdomain-names)\n of a Kubernetes object name. It is used by default as the name of the\n corresponding Google Cloud resource. If the `resourceID` field is\n supported in the Config Connector resource, you can specify a different\n name, which follows the naming convention of the Google Cloud\n resource, for the corresponding Google Cloud resource in the\n `spec.resourceID` field. For more information, see\n [Managing resources with the `resourceID` field](/config-connector/docs/how-to/managing-resources-with-resource-ids).\n\nNamespace\n: The namespace you create a Config Connector resource in determines the\n project that contains the Google Cloud resource. For more on\n namespaces, see\n [Kubernetes Namespaces and Google Cloud Projects](/config-connector/docs/concepts/namespaces-and-projects).\n\nLabels\n: Labels in the metadata field of a Config Connector resource are also added\n to the associated Google Cloud resource.\n: In addition, Config Connector adds a system label named `managed-by-cnrm`\n with a value of `true` to your Google Cloud resources.\n\nAnnotations\n: Config Connector can take additional actions on your resources that are\n not defined in the `spec`. These actions are defined in subfields of\n `metadata.annotations`. Annotation values *must* be a string.\n The types of annotations Config Connector supports\n are described in [annotations](/config-connector/docs/reference/annotations).\n\nFolders and hierarchical resources\n----------------------------------\n\nIn addition to managing resources in Google Cloud products,\nConfig Connector supports creating and managing resources within\nGoogle Cloud [Folders and Organizations](/resource-manager/docs/creating-managing-folders).\nFor more information, see [Namespaces and projects](/config-connector/docs/concepts/namespaces-and-projects).\n\nUsing RBAC for Access Control\n-----------------------------\n\nKubernetes\n[Role Based Access Control](https://kubernetes.io/docs/reference/access-authn-authz/rbac/)\n(RBAC) secures your resources. You can control creation of Google Cloud\nresources by assigning RBAC permissions. For more information, see\n[Securing access to resources](/config-connector/docs/how-to/securing-access-to-resources).\n\nStatus Condition\n----------------\n\nConfig Connector uses a ready condition in\n[`status.condition`](https://dev.to/maelvls/what-the-heck-are-kubernetes-conditions-for-4je7) for two purposes:\n\n- indicating when a resource is ready. When a resource is reconciled and ready, its `status.condition.status` will be set to `True`. To check when a resource is ready, see [Waiting for resources to be ready](/config-connector/docs/how-to/monitoring-your-resources#waiting_for_resources_to_be_ready)\n- displaying additional error or information. The ready condition has `Message` and `Reason` fields which provide additional information on the resource's status.\n\nEvents\n------\n\nImportant status changes for Config Connector resources are visible as\nKubernetes events. For more information, see\n[Viewing events](/config-connector/docs/how-to/monitoring-your-resources#viewing_events_for_a_single_resource).\n\nDeclarative configuration and eventual consistency\n--------------------------------------------------\n\nSee [Reconciliation](/config-connector/docs/concepts/reconciliation).\n\nWhat's next\n-----------\n\n- [Get started with Config Connector](/config-connector/docs/how-to/getting-started)\n- Learn about the [Resources](/config-connector/docs/reference/resources) that Config Connector configures."]]
