When the features.async.enabled flag of the CR is set to false, the Operator is checking that a CR corresponding to Microcks Kafka broker is not present. However for doing that, the Strimzi CRD must be defined on the cluster. Otherwise it raises an Error and makes the Operator crash.
This issue was not detected by our CI tests because we start creating a new cluster and setting up with dependency CRDs (Strimzi included). Then we start creating a CR with features.async.enabled to false. The test succeeds but we do not detect this hard dependency to CRD presence.
Changes have been published on quay.io/microcks/microcks-ansible-operator:latest. Please change your operator deployment image to this tag if you want to test it before 1.2.0 release.
When the
features.async.enabled
flag of the CR is set tofalse
, the Operator is checking that a CR corresponding to Microcks Kafka broker is not present. However for doing that, theStrimzi
CRD must be defined on the cluster. Otherwise it raises an Error and makes the Operator crash.This issue was not detected by our CI tests because we start creating a new cluster and setting up with dependency CRDs (Strimzi included). Then we start creating a CR with
features.async.enabled
tofalse
. The test succeeds but we do not detect this hard dependency to CRD presence.