-
Notifications
You must be signed in to change notification settings - Fork 179
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
Stop depending on default StorageClass' presence for ScyllaClusters in our manifests, examples, scripts and tests #2009
Stop depending on default StorageClass' presence for ScyllaClusters in our manifests, examples, scripts and tests #2009
Conversation
@rzetelskik: GitHub didn't allow me to request PR reviews from the following users: rzetelskik. Note that only scylladb members and repo collaborators can review this PR, and authors cannot review their own PRs. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/test e2e-gke-multi-datacenter-parallel |
6cdeb78
to
48effab
Compare
This is going to require explicitly setting /cc zimnx tnozicka |
48effab
to
cdb01e8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
/assign tnozicka
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cdb01e8
to
568554b
Compare
/lgtm /hold cancel /retest |
Description of your changes: This PR addresses the issue of ScyllaClusters in our manifests, examples, scripts and tests often depending on the presence of a default StorageClass. This is problematic because there can only be one, indicated with an annotation, so setting/unsetting a default tends to break immutability.
Simultaneously I've tried not to break existing workflows and not have to change all of our CI jobs by expecting a StorageClass to be set explicitly. Therefore:
scyllacluster-storageclass-name
flag, which defaults to empty string, which is then interpreted as falling back to default storageclass (not setting storageClassName),storageClassName
set toscylladb-local-xfs
by defaultSO_SCYLLACLUSTER_STORAGECLASS_NAME
which propagates to Scylla Manager's and tests' clusters; ifSO_SCYLLACLUSTER_STORAGECLASS_NAME
is explicitly set and empty,storageClassName
is not set, falling back to default storageclassWhich issue is resolved by this Pull Request:
Resolves #1990
/kind feature
/priority important-soon
/cc