Dashboard: See full Image name in Overview

[Globegitter]

Environment

Dashboard version: 1.6.3
Kubernetes version: 1.7.3
Operating system:
Node.js version:
Go version:

I am running this yaml file: https://github.com/kubernetes/kops/blob/fd6eb881b4a1901b5171ce07966c67f2b1fbda16/addons/kubernetes-dashboard/v1.6.3.yaml

Steps to reproduce

Launch a deployment with an image that has a very long name

Observed result

Name on overview dashboard gets cut off and not possible to see the full name.

Expected result

Some ability to see the full name, e.g. by hovering over it, to easily see what version is deployed

Comments

This is how it looks for basically all of our deplyoments:

[cheld]

Fundamentally, we have two options:

1. find a better presentation. Make it expandable somehow. (Maybe hover or Inbox style or something else.)
2. Remove information that is not absolutely required. It would be interessting to have some guidance from users which infromation they use and which information is obsolete.

[Globegitter]

Both are valid arguments - I like having this information in the overview to quickly check what image version this is using - maybe there is another option to have this customizable to users? But maybe that also just adds unnecessary bloat.

Not sure what the best solution here is but if the information does stay it would definitely be great to have something along the lines of 1. what you mentioned.

[cheld]

Customization is a good point. We can do so after we implemented a settings page. Currently, Dashboard is completely stateless.

So, you are actually interessted in the versions. This makes sense. (Of course, the versions require the image name and we cannot really remove any unneeded information)

[signalnerve]

Hi all! I'd like to get started contributing to the k8s dashboard and this ticket stood out to me today–would y'all be amenable if I fixed this via CSS? Modifying the text class white-space property on hover looks like this, locally:

[maciaszczykm]

@imkmf I think there could be overlays if there is less space vertically. Also, this could cause a lot of flickering.

[floreks]

There is already PR open for this #2330.

[cheld]

@imkmf the video is certainly nice. A few comments:

1. we have many resources that are potentially cut. Not only image names. e.g. labels, annotations.... if we apply this everywhere, I could imagine that any mouse movement would cause the layout to jump arround. I assume one would want a longer delay than in the video.
2. In the video the space below the image name is empty. However, a pod may have multiple containers. What happens with the text that is potentially below the image name?
3. Some resources can theoretically get very, very long. Not sure if this approach would work in a scenario where the expanded text is much longer than in the video. Of course, resources with maximum length are rather unlikely, but we should consider
4. It is not mobile compatible

Of course, small improvements are better than no improvements. I tend to believe the best solution would be similar to "Google Inbox": In table view the elements are listed with limited amount of information. A single click on a element does not leave the list view, but vertically expand the selected element. Of course, this is much more work - help is very welcome :)

[signalnerve]

Really good points @cheld! I'll check out the Google Inbox solution and see if it's feasible to put something together like that.

[cheld]

https://github.com/kubernetes/dashboard/issues/2048

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[rahulb3521]

Hi @maciaszczykm is anybody working on this issue currently, if not can I take this up and try it out

[maciaszczykm]

@rahulb3521 Sure, take it.

[maciaszczykm]

/unassign @rahulb3521

[floreks]

This does not happen anymore as we break image name into multiple lines if there is not enough space.

/close

[k8s-ci-robot]

@floreks: Closing this issue.

In response to this:

This does not happen anymore as we break image name into multiple lines if there is not enough space.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.