Related to this closed bug: https://issues.redhat.com/browse/OSSM-4009

Steps to reproduce:

• Install OSSM 2.4.0 operator (This is for sure happening in oldest versions)
• Install SMCP 2.4
• Wait until the SMCP is ready and all the pods are deployed
• Delete the SMCP
• Wait until all the pods are deleted
• Install the SMCP again

Result:

The Kiali pod is not deployed

What is happening is that the Kiali CR is not deleted fast enough and the SMCP is deleted, so when you are going to create the new SMCP verify that kiali CR exist and does not create the CR, when the pod is tried to be create there is not Kiali CR so the pod it's not created

Expected Behavior:

1. If the SMCP have Kiali enable should not be ready until kiali pod is created
2. SMCP deletion should be wait until all the resources are deleted