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

Creating cluster with 'volumeSpec' does not include default storageClass #168

Closed
kalium99 opened this issue Nov 28, 2018 · 2 comments
Closed
Labels
Milestone

Comments

@kalium99
Copy link

kalium99 commented Nov 28, 2018

Not sure if this is a bug or expected behaviour (perhaps the latter), but I copied the example in the docs for the optional volumeSpec, modifying only the value for storage:

volumeSpec:
    accessModes: [ "ReadWriteOnce" ]
    resources:
      requests:
        storage: 20Gi

This fails though due to having no storageClassName (which took me a few minutes to work out). I guess I should have known better, but maybe even mentioning storageClassName in the example docs may help (or even adding adding default storageClassName if none is present?).

@calind calind added this to the 0.2.3 milestone Jan 7, 2019
@calind
Copy link
Member

calind commented Jan 14, 2019

We expect that the cluster has a default storage class configured. If that's not the case, you can specify the storageClassName inline.

@AMecea
Copy link
Contributor

AMecea commented Jan 29, 2019

We add some documentation about this in #215

As @calind said the operator expects that the default storage class is configured, otherwise you should specify the storageClassName.

@AMecea AMecea closed this as completed Jan 29, 2019
chapsuk pushed a commit to chapsuk/mysql-operator that referenced this issue Oct 16, 2023
Signed-off-by: Peter Farr <Peter@PrismaPhonic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants