Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Improve traffic section in kn service describe #1590

Open
Tracked by #1588
rhuss opened this issue Jan 27, 2022 · 5 comments
Open
Tracked by #1588

Improve traffic section in kn service describe #1590

rhuss opened this issue Jan 27, 2022 · 5 comments
Assignees
@vyasgun
Labels
kind/enhancement triage/accepted Issues which should be fixed (post-triage)

Comments

@rhuss
Copy link
Contributor

rhuss commented Jan 27, 2022

The traffic section kn service describe is confusing as it uses a lot of shortcuts that are not explained anywhere and some revisions appear multiple times (once for when tagged, and one if latest)

[more details to be added ...]
@rhuss rhuss mentioned this issue Jan 27, 2022
Open
3 tasks
@github-actions
Copy link

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2022
@rhuss
Copy link
Contributor Author

rhuss commented Apr 28, 2022

/remove-lifecycle stale

@knative-prow knative-prow bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 28, 2022
@dsimansk
Copy link
Contributor

/kind good-first-issue

@knative-prow knative-prow bot added the good first issue Denotes an issue ready for a new contributor. label Jul 14, 2022
@rhuss
Copy link
Contributor Author

rhuss commented Jul 21, 2022

Well, not sure if this is a "good first issue". Technically it's easy, but it takes some UX experience and background knowledge to get push the description section in the right direction. Maybe we should first discuss here, how we would like the output to look like, and then the implementation should be straight forward.

@rhuss rhuss added triage/accepted Issues which should be fixed (post-triage) and removed good first issue Denotes an issue ready for a new contributor. labels Aug 16, 2022
@dsimansk dsimansk mentioned this issue Aug 16, 2022
Open
@vyasgun
Copy link
Contributor

vyasgun commented Aug 23, 2022

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@vyasgun vyasgun

Labels
kind/enhancement triage/accepted Issues which should be fixed (post-triage)
Projects
Client Planning
Status: Backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rhuss @dsimansk @vyasgun