Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create proposal on how to abstract the workflow Runner definition #559

Open
mszostok opened this issue Nov 15, 2021 · 0 comments
Open

Create proposal on how to abstract the workflow Runner definition #559

mszostok opened this issue Nov 15, 2021 · 0 comments
Labels
area/documentation Related to all activities around documentation area/engine Relates to Engine enhancement New feature or request needs-triage Relates to issues that should be refined

Comments

@mszostok
Copy link
Member

mszostok commented Nov 15, 2021

Description

Currently, we are hard-coded to the Argo Workflows, which is our only built-in runner. As a result, we are also tight to Kubernetes. This is against our decision of making Capact generic. We should create abstracted workflow definition which can be implemented by others. Maybe we can do it base on already existing spec, e.g. https://serverlessworkflow.io/

Additionally, we need to figure out how to extract and share the common logic between different runners (e.g. Interface resolution).

Reason

Make Capact platform-agnostic - enable implementing Engine for other platforms.

Use cases

  • User - enables them to use Capact with different engines, e.g. Kubernetes/bare-metal etc. and avoids platform-lock.
  • Capact Developer - gives an option to create alternative engines, e.g. bare-metal. Now you need to bootstrap the whole k8s cluster to be able to just execute a single action.
@mszostok mszostok added enhancement New feature or request area/engine Relates to Engine area/documentation Related to all activities around documentation needs-triage Relates to issues that should be refined labels Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/documentation Related to all activities around documentation area/engine Relates to Engine enhancement New feature or request needs-triage Relates to issues that should be refined
Projects
None yet
Development

No branches or pull requests

1 participant