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

View ConfigMaps Data will disappear after several secondes #4311

Closed
autherlj opened this issue Sep 20, 2019 · 2 comments
Closed

View ConfigMaps Data will disappear after several secondes #4311

autherlj opened this issue Sep 20, 2019 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@autherlj
Copy link

autherlj commented Sep 20, 2019 •
edited
Loading

Environment
Installation method: 
Kubernetes version: 1.15.0
Dashboard version:  2.0.0.bate4
Operating system: Centos7.3
Node.js version ('node --version' output):
Go version ('go version' output): go1.12.5
Steps to reproduce

Click Config Maps and view any config Data will disappear after several secondes

Observed result

kubectl apply -f recommended.yaml
Dashboard page chaos if you not refresh the page.
image

Expected result

page display normal

Comments

A user experience suggestion: CPU MEM Usage display can direct show numbers, not need to put mouse.
@autherlj autherlj added the kind/bug Categorizes issue or PR as related to a bug. label Sep 20, 2019
@autherlj autherlj changed the title View Congif Maps Data will disappear after several secondes View ConfigMaps Data will disappear after several secondes Sep 20, 2019
@maciaszczykm
Copy link
Member

Fix will be part of the new release.

@mausch
Copy link

mausch commented Oct 15, 2019 •
edited
Loading

duplicate of #4092

@AndySkyL AndySkyL mentioned this issue Oct 26, 2019
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mausch @maciaszczykm @autherlj