Skip to content

kubectl get crd shows CREATED AT instead of AGE (Inconsistency) #1832

@Mujib-Ahasan

Description

@Mujib-Ahasan

What happened?

kubectl get crd produces output with a CREATED AT column containing the full timestamp:

NAME                                    CREATED AT
analysisruns.argoproj.io                2026-03-13T19:37:41Z
analysistemplates.argoproj.io           2026-03-13T19:37:41Z
applications.kro.run                    2026-01-11T18:51:58Z
clusteranalysistemplates.argoproj.io    2026-03-13T19:37:41Z
dummies.kro.bug                         2026-01-11T20:19:45Z

However, most of the other kubectl get commands display an AGE column derived from the same metadata.creationTimestamp. I think AGE might be more intuitive and consistent with other kubectl get outputs than CREATED AT.

Expected behavior:

For consistency with other kubectl get outputs, it might be preferable to use AGE instead of CREATED AT or clarify if the current behavior is intentional.

/assign

Metadata

Metadata

Assignees

Labels

needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions