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

Error when attempting to get logs of a pod with >1 container is ugly #1493

Closed
paulbellamy opened this issue May 12, 2016 · 3 comments
Closed

Error when attempting to get logs of a pod with >1 container is ugly #1493

paulbellamy opened this issue May 12, 2016 · 3 comments
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer dogfood Important for the developer's own use of the project help-wanted An issue that would be good for non-maintainers to attempt
Milestone
Backlog

Comments

@paulbellamy
Copy link
Contributor

You have to hover and read the tooltip, which is ugly. Maybe we should hide/disable the control when there are multiple containers?
screen shot 2016-05-12 at 16 24 13
@paulbellamy paulbellamy added component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer dogfood Important for the developer's own use of the project labels May 12, 2016
@rade rade added the chore Related to fix/refinement/improvement of end user or new/existing developer functionality label Jul 4, 2016
@rade
Copy link
Member

rade commented Aug 27, 2016

Maybe we should hide/disable the control when there are multiple containers?

Not sure. It would make them less discoverable.

@paulbellamy
Copy link
Contributor Author

Disabling it makes it discoverable, but stops the user getting the error (in this case). Really we need a better way to display errors for controls.

@davkal davkal added the help-wanted An issue that would be good for non-maintainers to attempt label Oct 14, 2016
@rade rade modified the milestone: Backlog Jan 10, 2017
@rade rade mentioned this issue Jun 28, 2017
Closed
@rade rade mentioned this issue Jul 14, 2017
Closed
@rade
Copy link
Member

rade commented Jan 14, 2018

This got resolved by #3013

@rade rade closed this as completed Jan 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer dogfood Important for the developer's own use of the project help-wanted An issue that would be good for non-maintainers to attempt
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@rade @paulbellamy @davkal