Template-level semaphore #1528
faraguna-ginkgo
started this conversation in
Show and tell
Replies: 1 comment
-
|
This also shows the barebones of how we approached composability / modularity with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
At Ginkgo we had one particular computational protein engineering tool that was limited in the number of parallel executions we could run through it. There was a license server we could ping using a small, CPU-only upstream Task in the DAG, but the server update cadence was too slow to be useful. Our argo-native approach was a template-level semaphore. Importantly, we wanted this semaphore to limit the number of executions of a template across potentially many Workflows. This approach is covered here in the argo docs, but I didn't see any good actual examples in the hera docs (this was kinda close).
Our semaphore
Registering using e.g.
kubectl apply -f workflow-semaphore-config.yamlThen used with WorkflowTemplates like:
Please excuse any anti-patterns ;)
Beta Was this translation helpful? Give feedback.
All reactions