Finding a way to signal to the data plane that a particular managed kafka is in erronous state and it should be ignored: see the TODO comment on https://github.com/bf2fc6cc711aee1a0c2a/kas-fleet-manager/blob/5e6f90a4e64a128502bcbadaac076eeb9bd68481/internal/kafka/internal/services/kafka.go#L923 

We could do this using the avalable mechanism in the data plane since there is a managedkafka.bf2.org/pause-reconciliation - if that annotation is set, the fso will not update any of the dependent resources which can potentially be used. 
At the moment, this is not taken into account by the sync and the sync will still keep on trying to create the master secret for the instance. It might require an enhancement before this can be used.
That will be done by https://issues.redhat.com/browse/MGDSTRM-10879