-
Feature
-
Resolution: Won't Do
-
Minor
-
None
-
0
-
0%
-
Todo
Currently when the operator deploys the syndesis infrastructure, it basically creates necessary openshift resources at once and waits until everything is ready.
Some components require other components to be ready - for example while the syndesis server is starting, it is trying to connect to syndesis-db - when the syndesis-db is not ready yet, the deployment of the syndesis server errors out (and openshift will automatically retry it) - this can lead to 1-2 unnecessary restarts of syndesis-server until it is provisioned correctly.
It would be better, if the deployment had some logic in it, so that for example syndesis-server is started only after the syndesis-db is ready.