-
Notifications
You must be signed in to change notification settings - Fork 131
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
API Documentation for Testkube CRDs #3444
Labels
feature-request 🚀
New feature request
Comments
Hey @AndrewUnderwoodAtFanatics Right now we do a lot of efforts to improve our docs. This is really cool suggestion, guess @aabedraba and @tkonieczny will work on it |
This was referenced Mar 28, 2023
Hello @AndrewUnderwoodAtFanatics really good point and thanks for opening the issue. |
Related to #3537 (comment) Will be implemented by End of next week. |
This is blocked. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
In order to facilitate easier adoption of the GitOps deployment methodologies supported by Testkube it would be great to have solid documentation around what options are available for configuration in the Testkube CRDs.
I have a Git repo setup to deploy Test objects to my cluster via Flux, but now to write the Test definitions that I want to deploy, I need to manually create the test in the Testkube UI, go to settings, and export the test definition and tweak it to suit.
Describe the solution you'd like
More robust documentation of the CRDs would be helpful for those who want to approch the creation of tests from a GitOps perspective instead of via the UI or CLI. A subset of the existing test types do have CRD examples but not all and some are out of date, still showing
git-file
andgit-directories
as distinct options.I would hold the thoroughness of the FluxCD CRD documentation as goals to aim for:
https://fluxcd.io/flux/components/kustomize/kustomization/
https://fluxcd.io/flux/components/helm/helmreleases/
The text was updated successfully, but these errors were encountered: