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

Use explicit storageclass in all of our manifests #1990

Closed
tnozicka opened this issue Jun 24, 2024 · 0 comments · Fixed by #2009
Closed

Use explicit storageclass in all of our manifests #1990

tnozicka opened this issue Jun 24, 2024 · 0 comments · Fixed by #2009
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@tnozicka
Copy link
Member

Using a "wrong" storageclass happens too often. Also in production, users would specify the storage class explicitly, instead of making our storageclass to be the default for everything. (Cost-wise it's not needed for other apps.)

Let's wire all of our manifests and examples to use scylladb-local-xfs storageclass which makes it less error prone for us and our users.

CI wise, for cases where want to test a setup with different storageclass and alias may be a viable option without the need to edit all the configs in every CI job.

@tnozicka tnozicka added kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
2 participants