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

HTTP error while calling the API #8843

Closed
urbaman opened this issue Mar 28, 2024 · 2 comments
Closed

HTTP error while calling the API #8843

urbaman opened this issue Mar 28, 2024 · 2 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@urbaman
Copy link

urbaman commented Mar 28, 2024

What happened?

Just installed chart v7.1.3, accessed the dashboard, it seems to have the old (2.7.0) look and feel, and keeps loading workloads forever:

image

Then it sends an HTTP error calling the API

image

What did you expect to happen?

A working dashboard

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

helm upgrade -i kubernetes-dashboard kubernetes-dashboard/kubernetes-dashboard -n kubernetes-dashboard
kubectl port-forward -n kubernetes-dashboard services/kubernetes-dashboard-kong-proxy 8443:443

Anything else we need to know?

No response

What browsers are you seeing the problem on?

Chrome

Kubernetes Dashboard version

Chart 7.1.3

Kubernetes version

1.28.6

Dev environment

No response

@urbaman urbaman added the kind/bug Categorizes issue or PR as related to a bug. label Mar 28, 2024
@floreks
Copy link
Member

floreks commented Apr 5, 2024

Duplicate of #8835

/close

@k8s-ci-robot
Copy link
Contributor

@floreks: Closing this issue.

In response to this:

Duplicate of #8835

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

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

No branches or pull requests

3 participants