Replies: 1 comment 2 replies
-
WASM execution via this ArgoWF plugin could be one approach for serverless. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
For this question, I have searched through issues/discussions and found that Argo definitely doesn't support pod reuse, for example #5423.
I understand this might be due to reasons such as env isolation, since the task in each step is not a service. However, in most scenarios, I have multiple workflows that might share same tasks and my task is stateless. Therefore, I find it unnecessary to boot up a new container each time my workflow executes this step. I wonder, for a frequently called and stateless task, could the container possibly be reused?
I think the scenarios might be similar to using Step Function with Lambda, although I'm not very familiar with this. I guess that Lambda won't always cold boot when called by Step Function.
So currently, I'm considering the possibility of using OpenFaas with Argo, where OpenFaas handles the function lifecycle and Argo is used to schedule these serverless functions. However, the feasibility of this direction is not very clear to me, If anyone has had a similar idea or already has some experience with this, I would be very happy to learn.
Beta Was this translation helpful? Give feedback.
All reactions