-
Notifications
You must be signed in to change notification settings - Fork 178
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
Ephemeral Storage capacity change - Forbidden #1517
Labels
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
Comments
scylla-operator-bot
bot
added
the
needs-priority
Indicates a PR lacks a `priority/foo` label and requires one.
label
Nov 1, 2023
This issue is inherited from Kubernetes StatefulSets (see kubernetes/kubernetes#68737) the workaround is suggested in #825 Closing as dupe of #1103 |
I was changed this values in the chart scylla but when I install it then it is error
can you help me, please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment:
AWS EKS : latest
Scylla Operator : v1.11
Setup: 5 node cluster ( 1:1 scylla node to EKS node) with XFS storage on the NVME disk on the instance.
Storage type : ephemeral
Issue: underlying EKS node instance has enough storage . Attempt to increase the storage capacity in scylla.yaml resulted in below error.
Is this a bug report or feature request?
What should the feature do:
Increase the storage of the scylla node as permitted by the underlying ephemeral storage. When a cluster is operational with data, setting a capacity attribute be honored if the underlying ephemeral storage has enough volume to accomodate.
What is use case behind this feature:
If this is not supported, how else do we increase or replace the scylla nodes maximizing the storage capacity?
Additional Information:
The text was updated successfully, but these errors were encountered: