-
Notifications
You must be signed in to change notification settings - Fork 335
Enhance SandboxClaimStatus for Better Observability #963
Copy link
Copy link
Open
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes 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.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Metadata
Metadata
Assignees
Labels
kind/featureCategorizes issue or PR as related to a new feature.Categorizes 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.Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Backlog
What would you like to be added?
Add printer columns to
kubectl get sandboxclaimoutput.Why is this needed?
Currently, the
SandboxClaimresource provides very limited information in its status. When you runkubectl get sandboxclaim, you only see the age of the resource: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 sandboxclaimoutput.The
SandboxClaimStatusalready tracks enough information to surface useful columns. The output should look like:Proposed Columns:
status.conditions[type=Ready].statusstatus.sandbox.nameSandboxresourcestatus.conditions[type=Ready].reasonThe
REASONcolumn is a valuable addition — it surfaces the condition reason directly in the list view, eliminating the need to runkubectl describeto diagnose a stuck or failed claim.