unified or no DB dependency
Describe the solution you'd like
currently, we are considering the kubeshop tool testkube and tracetest. Both use different storage backends to store configurations, either postgres or mongoDB, which would add a lot burden for the operations to take care individual DB techstacks running.
Is there a way to unify the DB requirements or relax them with other storage options always available like the k8s API (especially for configurations, but not always suited for state. Or S3 which typically is always available for artifacts.
Additional context Note: Given our air gapped use case, "Cloud" is not an option.
kubeshop/tracetest#3141
hey @hwinkel Artifacts and logs are stored by default in Minio or S3 directly, Minio supports multiple storages behinds the scene we should have an issue in backlog about using ODBC data sourcesto decouple from MongoDb, technically it's a very simple database, but priority is a question for @TheBrunoLopes And we already can store test and test suite execution result in a special CRD
hey @hwinkel FYI: Testkube Cloud doesn't need storage at all - everything is stored in Testkube Cloud
as mentioned above, Cloud is not an option in a air gapped use case and restricted gov infrastructure
Hello @hwinkel have your considered our enterprise offering ? if you have a few minutes I wouldn't mind jumping on a quick call and giving you a quick walkthrough, we may be able to help you with your storage options.
Let me know which time works best for you or feel free to book a few minutes using this link: https://calendly.com/bruno-at-kubeshop/30min-1 ;)
as mentioned above, Cloud is not an option in a air gapped use case and restricted gov infrastructure
Hi @hwinkel we started recently Testkube Enterprise - it's cloud but run on-prem in infra owned by you. Bruno can describe it more for sure.