-
Notifications
You must be signed in to change notification settings - Fork 600
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regroup additional printer columns #3770
Regroup additional printer columns #3770
Conversation
- Put READY and REASON columns at right most position
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you argue a bit about the reasons? Also, k8s objects tend to put the Age
as last column.
@@ -38,18 +38,18 @@ spec: | |||
# see issue: https://github.com/knative/serving/issues/912 | |||
x-kubernetes-preserve-unknown-fields: true | |||
additionalPrinterColumns: | |||
- name: Ready |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@navidshaikh what's the motivation for this kind of re-grouping ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- The value for
REASON
could be empty if resource is READY, thus printing an empty column in between non empty columns - If resource is not
READY
, we can addreason:message
forREASON
column and keeping the variable length cell at the right (easy to parse) - To keep it consistent with how serving resources' fields are grouped
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the feedback, @navidshaikh
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matzew, navidshaikh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
Proposed Changes
READY
andREASON
columns at the right most position