Ensure ModuleTemplate CRD when missing

[kwiatekus]

Description

When CLI commands detect that ModuleTemplate CRD is missing, it should install it to enable usage of community modules on non-managed clusters.

kyma module catalog
Error:
  failed to list available modules from the target Kyma environment

Error Details:
  failed to list modules catalog: failed to query community modules: failed to list module templates: the server could not find the requested resource

Reasons

Community module use cases (listing catalog, listing installed modules, pulling, adding, deleting) should be available also on non-managed kyma clusters (i.e on k3d). ATM the lack of installed ModuleTemplate CRD is blocking it.

Attachments
Module template CRD

[ptesny]

kyma modules with non-SKR clusters (gardener, eks, aks, or even k3d)
I have installed both the ModuleTemplate CRD and the required module templates (CRDs) as depicted below:

kubectl get moduletemplate -A             
NAMESPACE     NAME                    AGE
default       registry-proxy-0.14.0   66m
kyma-system   api-gateway-3.4.1       66m
kyma-system   btp-operator-1.2.24     66m
kyma-system   istio-1.24.1            66m
kyma-system   serverless-1.9.5        66m
kyma-system   telemetry-1.54.0        66m

The outcome:

• the catalog subcommand renders all available kyma modules

kyma modules catalog
NAME              AVAILABLE VERSIONS   ORIGIN                            
api-gateway       3.4.1                kyma-system/api-gateway-3.4.1     
btp-operator      1.2.24               kyma-system/btp-operator-1.2.24   
istio             1.24.1               kyma-system/istio-1.24.1          
registry-proxy    0.14.0               default/registry-proxy-0.14.0     
serverless        1.9.5                kyma-system/serverless-1.9.5      
telemetry         1.54.0               kyma-system/telemetry-1.54.0      
cap-operator      0.22.0               community                         
docker-registry   0.10.0               community                         
registry-proxy    0.14.0               community   

• on the other hand, the list subcommand can only retrieve the installed community module(s)

kyma modules list   
failed to get installed manager: failed to retrieve manager info from telemetry: manager not found in resources
failed to get installed manager: failed to retrieve manager info from api-gateway: manager not found in resources
failed to get installed manager: failed to retrieve manager info from btp-operator: manager not found in resources
failed to get installed manager: failed to retrieve manager info from istio: manager not found in resources
failed to get installed manager: failed to retrieve manager info from serverless: manager not found in resources
NAME             VERSION   CR POLICY   MANAGED   MODULE STATUS   INSTALLATION STATUS   
registry-proxy   0.14.0    N/A         false     Warning         Ready 

Not sure why kyma cli errors with the manager not found in resources messages?

On a side note, that behaviour differs from in-cluster busola which can report some of these modules in the GUI (yet not all of them???)