[FEATURE] Support another technology to define and orchestrate the image creation inside a pod #1615
Labels
help wanted
Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
kind/feature
Categorizes issue or PR as related to a new feature.
Is there an existing feature request for this?
Is your feature request related to a problem or use-case? Please describe.
A use-case.
We want to explore the possibility of supporting another stack for delegating the image build inside a Pod. Most prominent example would be Argo Workflows.
Describe the solution that you would like.
A SHIP that can shed some light into this topic, using Argo Workflows. The SHIP besides providing a deep understanding of what aspects of the controller would need to be extended, should provide a concise explanation on why this is beneficial for our end users.
Describe alternatives you have considered.
None. We can explore other technologies besides Argo. But looking at the relevance, features and adoption from Argo, its definitely a good starting point.
Anything else?
In a nutshell, this could provide a proposal on how we can opt-in for another backend technology besides Tekton Pipelines.
The text was updated successfully, but these errors were encountered: