This message was deleted.

In most other Helm charts i worked with that also has it's own CRD's there is usually some "deployCRD=true/false" value that can be set, i'm not seeing that for the rancher-monitoring chart, for example cert-manager: https://github.com/cert-manager/cert-manager/blob/master/deploy/charts/cert-manager/values.yaml#L77

neuvector, rancher logging, and rancher monitoring all expect you to install the crds via a seperate helm chart, the setup you describe is how ive seen it deployed via fleet in multiple places, however you may want to add a

dependsOn:

for the main cattle-monitoring-system to depend on the crd install to complete first

Yeah that's what i've done so far adding the

dependsOn

however it's not optimal as it can result in a version skew where the monitoring chart deploys one version and the CRD chart another one if i don't make sure to update them both at the same time to the same version