Flux: Crash Report: Cannot read properties of undefined (reading 'names') on navigating to CustomResourceDefinition from Kustomization inventory

[whitespire]

Crash Summary

Client crash with "Cannot read properties of undefined (reading 'names')" error upon clicking on a link from Kustomization inventory leading to CustomResourceDefinition page.

Error Stack

TypeError: Cannot read properties of undefined (reading 'names')
    at extraSections (index-DD77KehG.js:1162:29756)
    at gi (index-DD77KehG.js:1143:12276)
    at xd (vendor-mui-CQMHlplZ.js:38:17652)
    at Nh (vendor-mui-CQMHlplZ.js:40:44746)
    at Eh (vendor-mui-CQMHlplZ.js:40:40337)
    at Ek (vendor-mui-CQMHlplZ.js:40:40265)
    at nc (vendor-mui-CQMHlplZ.js:40:40118)
    at Gd (vendor-mui-CQMHlplZ.js:40:36403)
    at Th (vendor-mui-CQMHlplZ.js:40:37215)
    at Eo (vendor-mui-CQMHlplZ.js:38:3274)

Headlamp Version

0.38.0

Flux Plugin Version

0.5.0

Git Commit

1c2f466a130403eeea04cba811bd597da5d61de1

Additional Context

Receiving this error when attempting to navigate to a HEADLAMP_BASE_URL/c/CLUSTER_NAME/crds/CRD_NAME link from Kustomization Inventory. Should be reproducible on any kustomization containing a custom resource definition manifest (tested on several different kustomizations and CRDs).

[whitespire]

Dev mode trace:

Uncaught TypeError: Cannot read properties of undefined (reading 'names')
 at extraSections (Details.tsx:92:38)
 at DetailsGrid (Resource.tsx:302:35)

After some digging on my end, noticed that, for some reason, the extraInfo that gets passed to DetailsGrid when going through the link has an extra nesting of jsonData compared to normal extraInfo (jsonData.jsonData). This may be an issue with Headlamp itself and not Flux, although I was unable to reproduce the issue with any native CRD links.

[ashu8912]

Thanks for reporting this @whitespire I am looking into this