Conversation
To control the flow of application deployments adding a count to the app of apps pattern should help with deployments. Each application's counter will +1 from the previous applications and theoretically should wait for that application to be healthy/synced before deploying.
|
There are two possible problems:
Scenario #1 is reasonably ok. I think most people, even without opening clusterGroup would see that M hasn't started syncing yet and try adjusting the order. Would adding ordering affect any existing patterns? Would scenario #2 be just as broken without this change? |
|
Can we rely on the order of appearance in the values file to make the assignation? What if it's just allowed to put the wave number in the values file so the end-user has the control of them so it can even ordered and group them as their convenience? |
|
This issue was opened long time ago, and dependencies between apps is something that is a must. In example: we could need (in a not so theoretical use case) to configure Local Storage Operator before configuring Openshift Data Foundation before configuring Quay registry. |
To control the flow of application deployments adding a count to the app
of apps pattern should help with deployments. Each application's counter
will +1 from the previous applications and theoretically should wait for
that application to be healthy/synced before deploying.