You can list the resources that Config Connector manages with, by running
the following command:
kubectl get gcp
Determining a resource's status
You can determine if your resource is ready by looking at its
status.condition.
Config Connector updates the status to reflect the current state of
your resource.
kubectl wait --for=condition=READY KINDNAME
Replace the following:
KIND: your resource's kind. For example, PubSubTopic.
NAME: your resource's name
Viewing events
Config Connector creates Kubernetes events with information and errors about
managing resources. You can view events for a specific resource, or all events
in your Config Connector environment.
Viewing events for a single resource
You can view the events for a single resource by examining the Events field
in the output of the following command:
kubectl describe KINDNAME
Replace the following:
KIND: your resource's kind
NAME: your resource's name
For example, if you had a Config Connector SQLInstance resource
named sqlinstance-sample, use the following command to view its events:
kubectl describe sqlinstance sqlinstance-sample
Viewing events for a namespace
To see the events for all Kubernetes resources in a given namespace, including
your Config Connector resources, run the following command:
kubectl --namespace CC_NAMESPACE get events
Replace CC_NAMESPACE with the namespace Config Connector
manages resources from.
Config Connector-specific events
Config Connector can create the following event types:
Updating
Occurs when a Config Connector resource's underlying Google Cloud
resource is being updated.
UpToDate
Occurs when a Config Connector resource's reconciliation has succeeded.
This event type means that the underlying Google Cloud resource now
matches the desired state specified by the Config Connector resource.
UpdateFailed
Occurs when a Config Connector resource's reconciliation has failed.
DependencyNotReady
Occurs when a referenced Config Connector resource is not ready. You can
determine whether a resource is ready by checking its
status.
DependencyNotFound
Occurs when a referenced Config Connector resource or Kubernetes Secret
is not found.
DependencyInvalid
Occurs when a reference is invalid. For example, suppose a Config Connector
resource that references a Kubernetes Secret. If the Secret exists, but if
it does not contain the key that is being referenced, then the reference
is said to be invalid.
Deleting
Occurs when Config Connector resource is being deleted from the Kubernetes
API Server.
Deleted
Occurs when a Config Connector resource has successfully been deleted from
the Kubernetes API Server.
DeleteFailed
Occurs when a Config Connector resource has failed to be deleted from the
Kubernetes API Server.
ManagementConflict
Occurs when a Config Connector resource fails to take ownership of the
underlying Google Cloud resource. When this occurs, it is usually
because another Config Connector resource already has ownership of the
Google Cloud resource. Read more about how Config Connector handles
conflicts between multiple Config Connector resources.
PreActuationTransformFailed
Occurs when a Config Connector resource fails to perform pre-actuation transformations.
This event type likely means that the resource configuration is invalid.
PostActuationTransformFailed
Occurs when a Config Connector resource fails to perform post-actuation transformations.
Unmanaged
Occurs when Config Connector is in
namespaced-mode
and the Config Connector resource is in a namespace where Config Connector
is not enabled (that is, the namespace does not have a
ConfigConnectorContext object).
This event can occur even if the namespace does have a
ConfigConnectorContext if the ConfigConnectorContext was created around
the same time as the Config Connector resource. You just need to wait
some time for Config Connector to start managing the resource.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 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)."]]