MicroK8s v1.2.5.0 - kubernetes-dashboard 404's cron Jobs

[Barfooss]

Summary

The packaged version of the kubernetes-dashboard in MicroK8s v1.25.0 is incompatible with the kubernetes api-version for listing Cron Jobs, resulting in a 404 response if navigating to "Cron Jobs" in the Dashboard.

What Should Happen Instead?

A List of the configured Cron Jobs in the namespace should be displayed.
See also bug report: kubernetes/dashboard#7289
And fixed in merge kubernetes/dashboard#7301

Reproduction Steps

Rollout microk8s v1.25.0, enable "dashboard", login to dashboard, click "Cron Jobs" in the left hand menu.

Introspection Report

inspection-report-20220917_130201.tar.gz

Can you suggest a fix?

Change version of packaged dashboard to 2.7.0

Are you interested in contributing with a fix?

no

<3

[trailblazn]

Thank you, I'm struggling with this issue too!

microk8s 1.25.0 and dashboard 2.6.0

Tried dashboard 2.7.0, same issue.

[trailblazn]

Finally, seems my issue was version mismatch too.

Resolved with dashboard 2.7.0 and

[neoaggelos]

Kubernetes Dashboard 2.6.0 and older is using batch/v1beta1 to access cronjobs, which is now removed in 1.25.

Dashboard 2.7.0 solves this issue, but there is still a minor bug when viewing the details a cronjob, which could be fixed by kubernetes/dashboard#7465

Once the bugfixes are released, we will make sure to update the image of the dashboard addon as needed.

In the meantime, you can fix the list of the cronjobs by manually updating the dashboard image:

microk8s kubectl set image -n kube-system deploy/kubernetes-dashboard kubernetes-dashboard=kubernetesui/dashboard:v2.7.0

[krichter722]

@neoaggelos FYI, I'm still experiencing the issue with kubernetesui/dashboard:v2.7.0 with microk8s v1.25.3 (snap 4094). The cronjob with apiVersion: batch/v1 is displayed in the list of cronjobs, but opening the details causes Not Found (404) the server could not find the requested resource. I have no trouble describing the cronjob with kubectl.

The issue was originally filed for the list of cronjobs which I can open, but I guess there's still a similar problem with the details now. Would you like me to file a separate issue for this. Do you have any idea if there's an upstream issue for the details already - I couldn't find one?

[neoaggelos]

Hi @krichter722

Dashboard version 2.7.0 fixes the issue with the cronjob list, but then, as you mentioned, opening an individual cronjob still fails with 404.

The linked PR kubernetes/dashboard#7465 fixes this and has been merged to master, but there still has not been a release that includes it yet. Supposedly, this will be release 2.7.1, and judging from the release cycle of the kubernetes dashboard project, it should come soon enough.

We are keeping an eye on it and will make sure to update the addon version accordingly.

[neoaggelos]

FYI; there is still no new k/dashboard release

[fontexD]

any update on this ? could be nice to be able to see the details of the cronjobs :)

[neoaggelos]

Hi @fontexD

Unfortunately, upstream has yet to release the fix kubernetes/dashboard#7465 (comment)

[fontexD]

I looked in the code for the cronjon and it seems fixed but last update was 6 month ago, was the fix already applied there? I could just compile current branch then and use it locally

[bhutkovskyysos]

I looked in the code for the cronjon and it seems fixed but last update was 6 month ago, was the fix already applied there? I could just compile current branch then and use it locally

that is what I'd like to do as well. Are there any instructions on how to compile it and build the docker image for it?

[sunnygupta3535]

Can we get at least a timeline of v2.7.1 of Kubernetes Dashboard? @bhutkovskyysos what approach you're following to resolve this issue?

[beffe123]

For everyone interested, I've created a fixed version based on kuberentes dashboard version v2.7.0. I've published it on docker hub: beffe/kubernetes-dashboard:v2.7.0-fix-cj-2

You can find the code changes here:
kubernetes/dashboard@master...beffe123:kubernetes-dashboard:v2.7.0-fixes

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.