helmRelease dry-run failed

[jack1902]

So i have a functioning helm-release wrapped within a kustomization which applies fine. However, with drift-detection enabled, i am getting errors coming out which i only see thanks to having alerts configured. Without those alerts in place, everything looks fine.

• kubectl get hr -n kafka - Release reconciliation succeeded is observed

I am getting alerts similar to the following:

helmrelease/kafka.namespace
KafkaConnect/kafka/my-connect-instance dry-run failed, reason: Invalid: KafkaConnect.kafka.strimzi.io "my-connect-instance" is invalid: spec.version: Invalid value: "null": spec.version in body must be of type string: "null"

The helmRelease itself is applied and functioning as i expect, but with drift-detection enabled i see the above error happening

relates to: #643

Additional Context

Logs from helm-controller

{"level":"error","ts":"2023-10-18T16:16:38.294Z","msg":"Reconciler error","controller":"helmrelease","controllerGroup":"helm.toolkit.fluxcd.io","controllerKind":"HelmRelease","HelmRelease":{"name":"kafka","namespace":"namespace"},"namespace":"namespace","name":"kafka","reconcileID":"527ad24d-5266-46e6-8fea-67306ccd0898","error":"KafkaConnect/kafka/my-connect-instance dry-run failed, reason: Invalid: KafkaConnect.kafka.strimzi.io \"my-connect-instance\" is invalid: spec.version: Invalid value: \"null\": spec.version in body must be of type string: \"null\"","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/[email protected]/pkg/internal/controller/controller.go:226"}

[hiddeco]

We shipped an improved version of the drift detection today in the v0.37.0 release. Can you maybe try and see if the newly added ignore rules feature helps with your problem?