-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
[Bug]: Two StorageClasses are set as default #1545
Comments
According to k3s-io/k3s#3445 (comment), the local-path provider is set as default on each reboot. Workaround: disable local-storage anyway and install it manually or through helm afterwards. |
@janfrederik But that's not a problem, is it? Just specify the class you want in your pvc definition. |
@mysticaltech Yes, when I have full control, I can always choose the storageclass in a pvc. Do you want me to create a pull request or do you prefer to drop this anyway? |
I created #1572 to mention this issue in the doc. That's the most pragmatic solution :-) |
Description
When setting
enable_local_storage = true
in kube.tf, two StorageClasses are created, as expected:However, both have annotation
"storageclass.kubernetes.io/is-default-class":"true"
.This is not what we want, because now it is unclear which one kubernetes will use.
Kube.tf file
Screenshots
No response
Platform
linux
The text was updated successfully, but these errors were encountered: