You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Only the workflow controller should be able to change a workflow.
Motivation
All these operations can result in invalid state one large workflows because they update the workflow out of the main loop.
Proposal
The controller currently reacts to pod and workflow changes, but it can already be reacting when a third-party changes - resulting in conflict and invalid state.
We could have a new operation queue that takes operations to workflows and ensures they are applied sequentially.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered:
alexec
changed the title
Resume/suspend/terminate/stop can result in invalid state
Resume/suspend/terminate/stop will result in invalid state
May 4, 2020
We could have a new operation queue that takes operations to workflows and ensures they are applied sequentially.
Also *Request CRDs as I mentioned in #6490 (comment) would very explicitly delegate to the Controller and would be queued (as the entire Controller is queued).
Summary
Only the workflow controller should be able to change a workflow.
Motivation
All these operations can result in invalid state one large workflows because they update the workflow out of the main loop.
Proposal
The controller currently reacts to pod and workflow changes, but it can already be reacting when a third-party changes - resulting in conflict and invalid state.
We could have a new operation queue that takes operations to workflows and ensures they are applied sequentially.
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: