Status Fields

Each Kubernetes resource that is mapped to a Konnect entity has several fields that indicate its status in Konnect.

Konnect native objects

Objects that are native to Konnect,they exist only in Konnect - have the following status fields:

• id is the unique identifier of the Konnect entity as assigned by Konnect API. If it’s unset (empty string), it means the Konnect entity hasn’t been created yet.
• serverURL is the URL of the Konnect server in which the entity exists.
• organizationID is the ID of Konnect Org that this entity has been created in.

To inspect these fields:

kubectl get <resource> <resource-name> -o yaml | yq '.status'

Example output:

conditions:
  ...
id: 7dcf6756-b2e7-4067-a19b-111111111111
organizationID: 5ca26716-02f7-4430-9117-111111111111
serverURL: https://us.api.konghq.com

These objects are defined under the konnect.konghq.com API group.

Kong Gateway configuration objects

Resources like KongConsumer, KongService, KongRoute, and KongPlugin configure Kong Gateway and are not native to Konnect. These are defined under the configuration.konghq.com API group and may be used with other controllers, such as Kong Ingress Controller.

When managed by Kong Operator for Konnect, Konnect-specific status fields appear under .status.konnect:

• controlPlaneID: The ID of the associated Konnect Control Plane.
• id: The unique ID assigned by the Konnect API. If empty, the entity hasn’t been created.
• serverURL: The URL of the Konnect server where the entity resides.
• organizationID: The Org ID under which the entity was created.

To inspect these fields:

kubectl get <resource> <resource-name> -o yaml | yq '.status.konnect'

Example output:

controlPlaneID: 7dcf6756-b2e7-4067-a19b-111111111111
id: 7dcf6756-b2e7-4067-a19b-111111111111
organizationID: 5ca26716-02f7-4430-9117-111111111111
serverURL: https://us.api.konghq.com

Resources also report status.conditions, where each condition carries a reason that explains the current state.

ConfigStoreRefValid on KongVault v2.3+

The KongVault reports the outcome of the reference in the ConfigStoreRefValid condition:

kubectl get kongvault <vault_prefix> -o jsonpath-as-json="{.status.conditions[?(@.type=='ConfigStoreRefValid')]}"

While the reference is unresolved, Kong Operator doesn’t push the KongVault to Konnect, so that a Vault is never created with a missing or wrong Config Store ID.