kubeshop
Unified or No Database 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.
@hwinkel I see Bruno has reached out to you to setup a call. If you can make the time later in the day, I would like to join (I am in CST time in USA). https://github.com/kubeshop/testkube/issues/4352#issuecomment-1713388131
