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
We are leveraging argo-workflows for flexible workflow scheduling and it works well, until we encountered use cases where many resources are going to be created representing many DAG nodes...
AFAIK, argo-workflows will create one pod for each node to wait for custom resources. Since Kubernetes might not work well with plenty of pods (like 10s of thousands), I wonder if these "dummy pods waiting for resource" can be further optimized? Will it be reasonable / doable to make argo-workflows controller to monitor the custom resources, rather than actual pods?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We are leveraging argo-workflows for flexible workflow scheduling and it works well, until we encountered use cases where many resources are going to be created representing many DAG nodes...
AFAIK, argo-workflows will create one pod for each node to wait for custom resources. Since Kubernetes might not work well with plenty of pods (like 10s of thousands), I wonder if these "dummy pods waiting for resource" can be further optimized? Will it be reasonable / doable to make argo-workflows controller to monitor the custom resources, rather than actual pods?
Any responses are appreciated!
Beta Was this translation helpful? Give feedback.
All reactions