[backport-1.4] Avoid getting irrelevant logs from rancher-turtles
Summary
Rancher-turtles is the solution responsible to import new workload clusters into rancher, in addition could be use to create/manage clusters throught capi-operator. This feature is disabled in our case, but the application behaviour is to always check if the CRDs related to capi-operator are installed and generate multiple warnings logs which are finally shipped into grafana.
I0724 08:38:52.570406 1 import_controller_v3.go:333] "agent is ready, no action needed" controller="cluster" controllerGroup="cluster.x-k8s.io" controllerKind="Cluster" Cluster="ba-rke2/ba-rke2" namespace="ba-rke2" name="ba-rke2" reconcileID="04446194-c0ed-4f6b-98df-21d0d32513ed"
E0724 08:38:59.637111 1 kind.go:71] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"AddonProvider\" in version \"operator.cluster.x-k8s.io/v1alpha2\"" logger="controller-runtime.source.EventHandler" kind="AddonProvider.operator.cluster.x-k8s.io"
E0724 08:38:59.642791 1 kind.go:71] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"ControlPlaneProvider\" in version \"operator.cluster.x-k8s.io/v1alpha2\"" logger="controller-runtime.source.EventHandler" kind="ControlPlaneProvider.operator.cluster.x-k8s.io"
E0724 08:38:59.647389 1 kind.go:71] "if kind is a CRD, it should be installed before calling Start" err="no matches for kind \"CoreProvider\" in version \"operator.cluster.x-k8s.io/v1alpha2\"" logger="controller-runtime.source.EventHandler" kind="CoreProvider.operator.cluster.x-k8s.io"We should avoid getting all the logs into grafana ( for a possible debug?) and filter them in order to get only relevant logs which are containing informations related to imported clusters and at the same time save the capacity from the storage point of view.