-
Notifications
You must be signed in to change notification settings - Fork 128
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
Architecture: rebase testkube ontop of argo-workflows #4069
Comments
thanks to @dejanzele and @TheBrunoLopes for our 2nd sync up meeting today on this topic and your sharing of current testkube dogfooding: TestKube helm release is tested using testkube, covering test kube api using postman executor, and playright executor (+ executor smoke tests)
|
Looks promising ! I got 2 questions (or suggestions maybe?) First when it comes to auth and authn ... would it be possible to stand on the shoulders of ArgoCD here ? Then we also have Argo Events, which I was looking to add in to the mix for triggering the right flow and coordination etc ... but when you describe it above it is not mentioned, would you care to elaborate as to why a bit ? LINKS |
Is your feature request related to a problem? Please describe.
As a testkube user,
In order to benefit from the features available in argo workflow that are missing in test kube,
I need testkube to leverage argo workflow while keeping differentiating testkube features
Currently, testkube is implementing its features on top of plain k8s api, generating Job and CronJob resources, with init container fetching git sources and custom triggers.
Describe the solution you'd like
TestKube to leverage argo workflows for most of the facilities, and focus on missing and test-specific features instead
Additional context
Following are some thoughts on requirements in my team for a test facade, and how testkube could leverage argo workflows to support them.
Actors:
Key desired features of an off the shelf K8S test framework
argo workflow details
trigger when changes to script/workflow content
argoproj/argo-workflows#8415 Conditionally Run Workflows Based on Git Artifact Files Changed
webui
Use cases
reuseable templates
https://github.com/argoproj-labs/argo-workflows-catalog/tree/master/templates few unmaintained templates
resulting test artifacts
https://argoproj.github.io/argo-workflows/artifact-visualization/
Prometheus metrics
https://argoproj.github.io/argo-workflows/metrics/
Trigger on git change
Likely through a webhook from the git repo provider (e.g. github or gitlab)
https://argoproj.github.io/argo-workflows/events/#workflow-template-triggered-by-the-event
https://argoproj.github.io/argo-workflows/webhooks/
https://argo-cd.readthedocs.io/en/stable/operator-manual/webhook/
CRD schema
Argo workflow CRD schema are currently empty because the schema size exceeds the K8S supported size. See argoproj/argo-workflows#8190 and argoproj/argo-helm#2105
Mount content from gitops repo
Related issues:
The text was updated successfully, but these errors were encountered: