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.

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

No items displayed in tables if clusterName set #6637

Closed
stephan2012 opened this issue Nov 25, 2021 · 5 comments · Fixed by #6647
Closed

No items displayed in tables if clusterName set #6637

stephan2012 opened this issue Nov 25, 2021 · 5 comments · Fixed by #6647
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@stephan2012
Copy link

stephan2012 commented Nov 25, 2021

Environment
Installation method: Helm chart
Kubernetes version: v1.19.16
Dashboard version (v1.x is not supported. Use v2.0 or later.): v2.4.0
Operating system: Ubuntu 18.04.6 LTS
Node.js version ('node --version' output): (official Docker image kubernetesui/dashboard:v2.4.0)
Go version ('go version' output): (official Docker image kubernetesui/dashboard:v2.4.0)
Steps to reproduce

When setting .settings.clusterName via Helm chart 5.0.4, the dashboard shows the number of elements, but no data in the tables (see attached screenshot).

k8s_dashboard_empty

The chart creates a configMap containing:

data:
  _global: '{"clusterName":"k8s"}'

Removing the setting (i.e., setting data to {}) makes the dashboard work.

Observed result

Dashboard shows the number of items, but no actual items.

Quite interesting: When doing many reloads of the page in the web browser, the dashboard sometimes shows data in the tables (every 6th to 10th attempt).

Expected result

Dashboard displays the cluster name and shows data. ;-)

Comments

Confused. Is there any documentation for the settings?

@stephan2012 stephan2012 added the kind/bug Categorizes issue or PR as related to a bug. label Nov 25, 2021
@floreks
Copy link
Member

floreks commented Nov 29, 2021

Duplicate of #6282

/close

@k8s-ci-robot
Copy link
Contributor

@floreks: Closing this issue.

In response to this:

Duplicate of #6282

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

@floreks
Copy link
Member

floreks commented Nov 29, 2021

Actually, my comment from #6282 (comment) is not solved. I will reopen to keep track of it.

/reopen

@k8s-ci-robot
Copy link
Contributor

@floreks: Reopened this issue.

In response to this:

Actually, my comment from #6282 (comment) is not solved. I will reopen to keep track of it.

/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Nov 29, 2021
@stephan2012
Copy link
Author

Well, after reading #6282 I’m really wondering why an externally provided config is not merged with the applications defaults. This is absolutely counterintuitive and I do not know any other recent application behaving this way. Instead, it is quite natural to only pass values that you want to override. This also improves forward compatibility when new settings are introduced for the dashboard. Just

helm config to contain all settings and a comment no to remove any of them

is really an attempt to cover bad application design. :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants