-
Notifications
You must be signed in to change notification settings - Fork 437
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
Does local-path super multiple sc for deffrence performance disk #254
Comments
I would say that you can create 2 or more installations of Local Path Provisioners each with different disks configured and with different names for each Storage Class. This way you can reference different disk types using specific SC. |
Thanks for your replay, |
apiVersion: v1 apiVersion: v1 apiVersion: rbac.authorization.k8s.io/v1
apiVersion: rbac.authorization.k8s.io/v1
apiVersion: apps/v1 apiVersion: storage.k8s.io/v1 kind: ConfigMap |
1 similar comment
apiVersion: v1 apiVersion: v1 apiVersion: rbac.authorization.k8s.io/v1
apiVersion: rbac.authorization.k8s.io/v1
apiVersion: apps/v1 apiVersion: storage.k8s.io/v1 kind: ConfigMap |
env:
|
I'm currently hitting the same thing, tbh this feels like it's semantically wrong. The point of a storage class is exactly to define classes of storage (i.e. fast=ssd, slower=hdd etc.) which may differ in parameters/options. I believe the provisioner should take the paths from the storage class definition rather than from the centralized config map. This way the paths/sharedFileSystemPath could be defined per storageClass and you don't need to have multiple provisioner pods running inside of the same cluster (in my case it's 5 installations of the provisioner which seems rather cumbersome...) A way to implement this in backward compatible way would be to let the user define these fields in both places and letting the storageClass behave as an override of the default values found in the configMap. |
Hi all, any chance the suggestion above would be considered or is it too much of a blast into current design? |
I think the |
This should be fixed by #306, I think. |
The setup and teardown scripts, helper pod image can also differ per storage class thus #306 is short-sighted solution. I would recommend giving up the ConfigMap as it is at the moment and move the scrpits into StorageClass definition |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
I have hdd and ssd installed in host server.
I want create two k8s storageclass to support for both hdd and ssd to adapt different performance requirement.
Is local-path supported this and how to do with it
The text was updated successfully, but these errors were encountered: