Dashboard: Kubernetes Dashboard ignores numer of Items after reordering

[msolefonte]

Environment

Installation method: Official YAML
Kubernetes version: 1.13.1
Dashboard version: 1.10.1
Operating system: Ubuntu 16.04
Browser: Firefox 64.0 (64bit)

Steps to reproduce

(I did this exactly with 50 nodes active)
Go to Settings and select a custom number of Items per page. After that, go to any view (as for example, Pods) and order the elements by something, like for example Age.

Observed result

There are listed only ten elements, as the default value of Items per page. Also, there is no possibility to select the next elements.

Expected result

To be able to see Itemps per page elements per page.

Comments

I will personally take a look to it because it seems to be something that developers forgot.

Edit:

Pictures

10/50 pods are shown, everything is ok

I select in Settings that I want to see 50 items per page

50/50 pods are shown, everything is ok

After sorting: 10/50 pods are shown. There is no possibility to see more elements.

[floreks]

I actually can not reproduce that. Tested right now on v1.10.1 and everything works fine. After selecting 15 items, I can use sorting, filtering and change list pages as expected.

[maciaszczykm]

Perhaps that has something to do with Kubernetes v1.13 not being compatible with our release: https://github.com/kubernetes/dashboard/releases/tag/v1.10.1

We are going to support it in v2.0.0.

[floreks]

I have tested it on k8s v1.13.1 so that is not it. Maybe it's an issue with privileges to read settings config map.

[msolefonte]

Update with pictures. Perhaps the problem is that, as there are 50/50 pods, navigation bar is not shown and, after sorting elements (which should not reduce Items per page), the bar is not drawn again.

[floreks]

@WolfyLPDC I am wondering if you're really using v1.10.1 version. I have checked exactly the steps you have described and everything is fine.

1. Default items per page
   

2. Changing to 50
   

3. Going to pods, everything looks fine
   

4. Changed sorting to by status
   

5. Pager still visible
   

[msolefonte]

I'm using 1.10.1. Take a look to the About view:

About
Dashboard
General-purpose web UI for Kubernetes clusters
Dashboard Version: v1.10.1
Git Commit: 50d59e985dfd97863a2f5ab5396ae049a2bb87d0

Have you do it in Firefox? It is strange. I do not think it is a bad installation.

[floreks]

I have tried on Firefox and Chrome, and cannot reproduce it also. It might only appear when dealing with real cluster under load, not my small local kubeadm cluster.

[msolefonte]

I'm using a test cluster in VirtualBox and there is no real load, so I do not think that it is the problem. I do not know what other information add here.

[floreks]

Can you try out head image and see if it still occurs?

$ kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/master/aio/deploy/recommended/kubernetes-dashboard-head.yaml

Access path should be (with kubectl proxy):

http://localhost:8001/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard-head:/proxy/

This is just to test this one thing. This image is just a preview of dashboard v2. Many things are not working correctly yet.

EDIT: Seems like our unstable head image is failing to start :slightly_smiling_face:. I will fix that ASAP

[msolefonte]

I'm going to be busy this weekend. Say me what should I try and Monday I'll send all the screenshots requested.

[msolefonte]

@floreks I have tried the image but still does not work. Do you have an update?

[floreks]

@WolfyLPDC Ye, I do have an update :slightly_smiling_face: Apparently client-go has introduced some breaking changes to the way in-cluster config works now and we have to refactor our code, to make it work again. I'll try to do it somewhere this week.

[msolefonte]

@floreks
Ok. Tag me if you want me to test it.

[floreks]

@WolfyLPDC could you follow instruction from my previous comment (https://github.com/kubernetes/dashboard/issues/3497#issuecomment-453512372) and retest? Head image should be fixed now.

[msolefonte]

@floreks Tested! It seems to work fine. Good job.

[floreks]

Great. It will be available in the next release. Thanks for testing.

/close

[k8s-ci-robot]

@floreks: Closing this issue.

In response to this:

Great. It will be available in the next release. Thanks for testing.

/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.