Cronjob UI tab not namespaced

[dal13002]

Describe the bug

As of this pull request, we can now select a namespace from the filter search bar on almost any page (pods, deployments, secrets, etc..) and all api calls are being scoped to that namespace. This is great since we don't have to modify / mange "accessible namespaces" for non-admin users. What I've noticed is this feature is not happening in the "cronjobs" tab, and I am still getting errors trying to access cronjobs when I filter to a certain namespace.

To Reproduce

Steps to reproduce the bug:

1. You have full access to "test" namespace and list all namespaces within the cluster
2. There is nothing configured in "accessible namespaces" setting
3. Create a cronjob in "test" namespace (ie use kubectl)
4. Go to cronjob tab on headlamp -> add "test" to the namespace filter
5. The UI seems to just load forever

Environment (please provide info about your environment):

• Installation type: In cluster using helm
• Headlamp Version: v0.27.0

Are you able to fix this issue?

No

Additional Context

N/A

[skoeva]

Hi, are you still experiencing this issue? If so, would you be able to share more info about it (i.e. how long the table takes to load, how many cron jobs you have configured, or anything else that might be helpful)

[dal13002]

Hi,
Yes I still see this issue. I have only 1 cronjob and it will load forever (the load icon never goes away). Basically:

• if I give myself cluster-admin access, page will load immediately and I will see the 1 cronjob
• if I give myself admin to just the "test" namespace (where the one cronjob lives), and list all namespaces permission- I can select the "test" namespace from the filter menu. But it will load forever. If I look at the network tab, I see 403 forbidden while calling api/batch/v1/cronjobs. I think this api call should be namespaced but it is not- for example, when I select the "test" namespace it should be calling something like api/batch/v1/namespace/test/cronjobs (I don't know the internal endpoints but something like that so it only targets that namespace the same way "pods" work)