Kubernetes dashboard fails on Resources with `proxy` in name

St4NNi commented 1 year ago

What happened?

If we try to access a resource that has the term proxy in its name or kind, access through the regular kubernetes dashboard will fail with the following error:

Unknown error (200)
Http failure during parsing <URL>

This issue seems to be related to the way kubermatic forwards access to the dashboard and is not a problem in the dashboard itself. It looks like the URL parsing gets confused with more than one occurences of the term proxy in the forwarded URL.

Expected behavior

Show resources that contain the string proxy in their URL (name / kind / apiversion).

How to reproduce the issue?

Create any resource that contains the term proxy. Like Envoy Proxy or a deployment with proxy as its name: kubectl create deploy proxy --image nginx
- Try to view the resource in the Dashboard:

unknownerror

Renaming the resource to something different will fix the problem.

How is your environment configured?

KKP version: v2.21.6
Shared or separate master/seed clusters?: Shared clusters

Provide your KKP manifest here (if applicable)

Unfortunately I do not have access to the KKP manifest.

What cloud provider are you running on? Openstack

What operating system are you running in your user cluster? Ubuntu 20.04 / 22.04

kubermatic-bot commented 8 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

St4NNi commented 8 months ago

/remove-lifecycle stale

kubermatic-bot commented 5 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

St4NNi commented 5 months ago

This is still an issue. Is there any intention to fix this ?

/remove-lifecycle stale

kubermatic-bot commented 2 months ago

Issues go stale after 90d of inactivity. After a furter 30 days, they will turn rotten. Mark the issue as fresh with /remove-lifecycle stale.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubermatic-bot commented 1 month ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubermatic-bot commented 1 week ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubermatic-bot commented 1 week ago

@kubermatic-bot: Closing this issue.

In response to [this](https://github.com/kubermatic/dashboard/issues/6003#issuecomment-2495715611): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

kubermatic / dashboard