[GitHub] [submarine] Kenchu123 commented on pull request #707: SUBMARINE-975. Create storageClass for database, minio, tensorboard to control persistentVolume

[GitBox <gi...@apache.org>]

Kenchu123 commented on pull request #707:
URL: https://github.com/apache/submarine/pull/707#issuecomment-898894908


   > Thank @Kenchu123 for your contribution! I have a question. Why do we need the file`storageclass.yaml`? In my opinion, the hard-coded StorageClass names cannot support multi-tenancy. To elaborate, in your implementation, two Submarine services in two different namespaces will use the same name "submarine-database-sc" as the name of their DB StorageClass.
   
   Storage class is like an agent for controlling persistent volumes. Take submarine as an example, for submarine servers in different namespaces, they will have different persistent volume claims, so the storage class's provisioner will then create different persistent volumes for each submarine server.
   Besides, the storage class is cluster-scoped, so I think components in different namespaces can use the same storage class.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@submarine.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org