Skip to content

Enhance SandboxClaimStatus for Better Observability #963

@shrutiyam-glitch

Description

@shrutiyam-glitch

What would you like to be added?

Add printer columns to kubectl get sandboxclaim output.

Why is this needed?

Currently, the SandboxClaim resource provides very limited information in its status. When you run kubectl get sandboxclaim, you only see the age of the resource:

  $ kubectl get sandboxclaim my-claim
  NAME          AGE
  my-claim      45s

This makes it difficult to monitor claim health, quickly check stuck claims without inspecting the resource describe.

Proposed Solution

Add printer columns to kubectl get sandboxclaim output.

The SandboxClaimStatus already tracks enough information to surface useful columns. The output should look like:

 $ kubectl get sandboxclaim 
 NAME        READY   SANDBOX         REASON                                     AGE
 my-claim-1    False    my-claim-xk9z        WarmpoolNotFound              3s
 my-claim-2    True    my-claim-xk9y                                      3s

Proposed Columns:

Field Source Description
READY status.conditions[type=Ready].status True or False
SANDBOX status.sandbox.name Name of the underlying Sandbox resource
REASON status.conditions[type=Ready].reason Reason for current ready state
AGE Standard -

The REASON column is a valuable addition — it surfaces the condition reason directly in the list view, eliminating the need to run kubectl describe to diagnose a stuck or failed claim.

Metadata

Metadata

Labels

kind/featureCategorizes issue or PR as related to a new feature.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.

Type

No type
No fields configured for issues without a type.

Projects

Status
Backlog

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions