-
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
testkube operator integration as a flux controller #3026
Comments
Thank you @gberche-orange for such a thoughtful feature request. I wish, we would have all of them like yours :) |
Hello @gberche-orange awesome feature request. |
Here's an idea for a simple way to integrate the two in the short-term. If you allow TestTriggers to trigger tests on CustomResources, it would be possible to execute a Test on HelmRelease/Kustomization Conditions i.e. apiVersion: tests.testkube.io/v1
kind: TestTrigger
metadata:
name: testtrigger-example
spec:
resource: <HelmRelease|Kustomization>
resourceSelector:
namespace: foo-ns
name: my-helmrelease
event: <created|modified|deleted>
conditionSpec:
timeout: 100
conditions:
- reason: ReconciliationSucceeded
status: "True"
type: Ready
- reason: UpgradeSucceeded
status: "True"
type: Released
action: run
execution: test
testSelector:
name: test-to-run
namespace: testkube It's wonderful that TestTriggers already support labelSelectors as well. This would provide a good intermediate step to allow people to start using it and perhaps offer more suggestions for improvement. Seems like it could be doable in a reasonable amount of time as well. I'm very interested in this functionality and would be happy to share more ideas on this if needed! |
@TheBrunoLopes @vsukhin could you please share your current thoughts about fluxcd gitops toolkit usage by testkube ? Here is a refinement of possible UX for integrating flux devops toolkit into testkube: Test sources https://docs.testkube.io/articles/test-sources/ get extended to reference a fluxcd source CR ref
During test execution, the runner init container would fetch the cached source tar.gz archive from the source controller rest endpoint (see https://fluxcd.io/flux/gitops-toolkit/source-watcher/) and then copy into the The fluxcd source controller notifications would also support:
This would also likely increase tk scalability by reducing load on remote upstream sources, such as gitrepo serving monorepos (albeit existing tk shallow clones and sparse checkout), and leverage the existing extensive fluxcd sourcecontroller caching investments. In terms of market mindshare, this integration is likely to bring to testkube a large body of opensource flux users including enterprise customers. They're likely to express additional enterprise requirements that might help fuel the great testkube development efforts. |
Is your feature request related to a problem? Please describe.
testkube-operator does not seem to integrate yet well with flux ecosystem, for flux consumer projects :
Describe the solution you'd like
testkube operator to also be integrated as a flux extension, see https://fluxcd.io/ecosystem/#flux-extensions
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, CLI input/output, etc. about the feature request here.
The text was updated successfully, but these errors were encountered: