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

[karl18]

What happened?

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

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]

Same error in my cluster,

Kubernetes Dashboard version
v2.7.0
Kubernetes version
v1.25.4

[qmercier]

Same error in my cluster,

Kubernetes Dashboard version
v2.7.0
Kubernetes version
v1.25.6

[kaykhan]

Tried rolling back dashboard version, but no luck.

Has anyone found a work around for this problem?

[jnoordsij]

I think #7465 should have fixed this, but no new release has been made yet.

[Shivam0609]

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

[dannmartens]

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]

also waiting here on it :D

[davidroth]

Yeah same. Last release is 9 months old🥲

[mendy-lp]

Same here :(

[DiogoMCampos]

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

[maciaszczykm]

You can do some testing for #7969 if you want.

[fapinheiro]

Same error here.

Dashboard v2.7.0
Kubernetes 1.26.6

Any updates on this subject?

[fontexD]

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

master...beffe123:kubernetes-dashboard:v2.7.0-fixes

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

[furacas]

I temporarily fell back to version 2.6.1 to avoid this problem

[kaykhan]

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

[steveannett]

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]

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-triage-robot]

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

[marekhanus]

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]

@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]

A new release that will contain the fix should be available next week. There will be lots of other changes too. Ref: #8708

[k8s-triage-robot]

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

[liuqi-sun]

I have found out the cause of this problem, please refer to #9622