search

kubernetes / dashboard

General-purpose web UI for Kubernetes clusters
Apache License 2.0
14.08k stars 4.11k forks source link

CronJobs always show Unknown error (404) the server could not find the requested resource #7717

Closed karl18 closed 1 month ago

karl18 commented 1 year ago

What happened?

Cron Jobs Tab in the Dashboard always shows this error: Unknown error (404) the server could not find the requested resource

Screenshot 2023-04-26 at 10 55 01

Unfortunately, looks like it only happened after upgrading the k8s cluster to version v1.25.6 I’m using Kubernetes Dashboard chart version: v1.25.6

What did you expect to happen?

open the page normally as other tabs

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

Just opening CronJobs anytime, it shows the error above

pod logs:

2023/04/26 09:04:27 Getting list of all cron jobs in the cluster 2023/04/26 09:04:27 [2023-04-26T09:04:27Z] Outcoming response to 172.16.6.167 with 404 status code 2023/04/26 09:04:27 [2023-04-26T09:04:27Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 172.16.6.167: 2023/04/26 09:04:27 [2023-04-26T09:04:27Z] Outcoming response to 172.16.6.167 with 200 status code 2023/04/26 09:04:29 [2023-04-26T09:04:29Z] Incoming HTTP/1.1 GET /api/v1/namespace request from 172.16.6.167:

Anything else we need to know?

No response

What browsers are you seeing the problem on?

Chrome

Kubernetes Dashboard version

v6.0.7

Kubernetes version

v1.25.6

Dev environment

No response

yinyangsx commented 1 year ago

Same error in my cluster,

Kubernetes Dashboard version v2.7.0 Kubernetes version v1.25.4

qmercier commented 1 year ago

Same error in my cluster,

Kubernetes Dashboard version v2.7.0 Kubernetes version v1.25.6

kaykhan commented 1 year ago

Tried rolling back dashboard version, but no luck.

Has anyone found a work around for this problem?

jnoordsij commented 1 year ago

I think https://github.com/kubernetes/dashboard/pull/7465 should have fixed this, but no new release has been made yet.

Shivam0609 commented 1 year ago

Hello, can someone confirm when can we expect a new dashboard version with the fix ?

dannmartens commented 1 year ago

Hello, can someone confirm when can we expect a new dashboard version with the fix ?

Indeed, a patch update with this fix would be greatly appreciated!

fontexD commented 1 year ago

also waiting here on it :D

davidroth commented 1 year ago

Yeah same. Last release is 9 months old🥲

mendy-lp commented 1 year ago

Same here :(

DiogoMCampos commented 1 year ago

Hello, is there something the community can help with here to get it released? 😃

maciaszczykm commented 1 year ago

You can do some testing for https://github.com/kubernetes/dashboard/pull/7969 if you want.

fapinheiro commented 10 months ago

Same error here.

Dashboard v2.7.0 Kubernetes 1.26.6

Any updates on this subject?

fontexD commented 10 months ago

there is a guy that got tired of waiting (1 year now i think) with no updates on this so he fixed it himself within 5 min and uploaded his branch of the dashboard, and it works flawlessly :) here is a working version of k8s dashboard :) i dont know how many years it takes to fix this,, but this guy did it in no time alone xD

i wonder why a hotfix have not been released , the codechange is SO easy

https://github.com/kubernetes/dashboard/compare/master...beffe123:kubernetes-dashboard:v2.7.0-fixes

image : beffe/kubernetes-dashboard:v2.7.0-fix-cj-2

furacas commented 10 months ago

I temporarily fell back to version 2.6.1 to avoid this problem

kaykhan commented 10 months ago

Is there an existing PR with these changes, maybe we can up-vote that PR?

steveannett commented 10 months ago

The project has been restructured since these changes were originally made, and it seems they have now incorporated the necessary changes in, but not yet released. Both jobs.go and types.go have the modifications.

I assume we would have to wait for version 3.0.0 before the Cron Jobs tab works again

k8s-triage-robot commented 5 months ago

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

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

You can:

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

/lifecycle stale

k8s-triage-robot commented 4 months ago

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:

You can:

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

/lifecycle rotten

marekhanus commented 4 months ago

Hi @floreks, please could you release 2.7.1 with fix from #7465? I think that it will solve this issue.

The issue still persists and no 3.x release was made.

/remove-lifecycle rotten

jooosh commented 4 months ago

@marekhanus I was able to get an image built using the patch created by beffe123. The image is posted on docker hub. I make no guarantee that it won't blow up your k8s environment but it's running on ours without issue. 😉

floreks commented 4 months ago

A new release that will contain the fix should be available next week. There will be lots of other changes too. Ref: https://github.com/kubernetes/dashboard/pull/8708

k8s-triage-robot commented 1 month ago

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

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

You can:

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

/lifecycle stale