Skip to content
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

Unified or No Database dependency #3141

Open
hwinkel opened this issue Sep 9, 2023 · 2 comments
Open

Unified or No Database dependency #3141

hwinkel opened this issue Sep 9, 2023 · 2 comments
Labels
enhancement New feature or request triage requires triage user-request

Comments

@hwinkel
Copy link

hwinkel commented Sep 9, 2023

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 hwinkel added enhancement New feature or request triage requires triage labels Sep 9, 2023
@hwinkel
Copy link
Author

hwinkel commented Sep 9, 2023

kubeshop/testkube/#4352

@kdhamric
Copy link
Collaborator

@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). kubeshop/testkube#4352 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triage requires triage user-request
Projects
None yet
Development

No branches or pull requests

2 participants