On my local machine (m1 arm), when I try to apply a CR in dev mode, I get stucked in probe checks:

Warning   Unhealthy           pod/greeting-f6f998bc7-jmfvs    Startup probe failed: Get "http://172.17.0.9:8080/q/health/started": dial tcp 172.17.0.9:8080: connect: connection refused

With rhn-support-zanini guidance, when I put replica 0 on kogito-serverless-operator-controller-manager and removed the probes from CR, my workflow successful started.

Two suggestions:

• Enhance the number of probe executions before failure.

• In extreme cases, allow users to edit probe parameters.