This is caused when dynamic component generation of a connected Kubernetes cluster generates a component for the resource “CustomResourceDefinition”. When a CRD component is attempted to be used the following causes are in-action:
- the CRD component is schemaless, hence no form data to present.
- the Models API of Meshery Server should be filtering out (not returning) schema-less components to clients like Meshery UI/MeshMap.
An enhancement is needed in the Models API to change the default behavior to not return schema-less components.
