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

Node resource allocation graphs do not fit container #7733

Open
SoumyadeepOSD opened this issue May 14, 2023 · 3 comments
Open

Node resource allocation graphs do not fit container #7733

SoumyadeepOSD opened this issue May 14, 2023 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. kind/design Categorizes issue or PR as related to design.

Comments

@SoumyadeepOSD
Copy link

What happened?

Circular Pods allocation indicator escaped the background

image

What did you expect to happen?

Expectation: The circular resource allocation indicator must be placed inside the boundaries of the dashboard

How can we reproduce it (as minimally and precisely as possible)?

  1. Open Terminal or Powershell and type minikube dashboard and hit enter, you will be redirected to the dashboard
  2. In the Nodes section you will able to see the above mentioned issue

Anything else we need to know?

No response

What browsers are you seeing the problem on?

Microsoft Edge

Kubernetes Dashboard version

v2.7.0

Kubernetes version

v4.5.7

Dev environment

No response
@SoumyadeepOSD SoumyadeepOSD added the kind/bug Categorizes issue or PR as related to a bug. label May 14, 2023
@maciaszczykm maciaszczykm added the kind/design Categorizes issue or PR as related to design. label May 15, 2023
@maciaszczykm maciaszczykm changed the title minikube dashboard UI fix Node resource allocation graphs do not fit container May 15, 2023
@frozenprocess frozenprocess mentioned this issue Jun 1, 2023
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 19, 2024
@vaibhav2107
Copy link
Member

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Mar 12, 2024
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. kind/design Categorizes issue or PR as related to design.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix: Responsive Node charts frozenprocess/dashboard
5 participants
@maciaszczykm @k8s-ci-robot @k8s-triage-robot @vaibhav2107 @SoumyadeepOSD