In the new Flux overview page the CRDs are queried from the K8s API server. This might give problems in K8s clusters that are locked down for developers.

E.g. environments where developers get restricted permissions to edit resources in their own namespaces, manage flux CRs in their own namespaces, but they get NO permissions to view the CRD (kubectl get get crd kustomizations.kustomize.toolkit.fluxcd.io). In enterprise environments this kind of setup is not uncommon.

Instead, we could directly call makeCustomResourceClass(), e.g.

 makeCustomResourceClass({
    apiInfo: [{ group: kustomizationGroup, version: kustomizationVersion }],
    isNamespaced: true,
    singularName: 'Kustomization',
    pluralName: 'kustomizations',
  });

The flux list and detail pages allready use this approach.