Open braghettos opened 4 years ago
It seems that Rancher integrated those providers into their own solution, not the providers themselves (that is, your feature request is for Rancher; Trident is open source, any one can integrate it into their software as long as they respect the license)
@braghettos If you have a contact at Rancher please ask them to comment on this GitHub issue. It may be as simple as providing a YAML/JSON file.
@scaleoutsean : could you please explain me the detail about the licence? @gnarl : I have some contacts, I'll try to understand which type of file they want!
@braghettos I meant the LICENSE
entitles any licensee to pull/copy/republish Trident (or its parts) in their s/w.
K8S Internal Storage Class providers are enlisted here: https://kubernetes.io/docs/concepts/storage/storage-classes/#provisioner. Trident is not shipped as an internal provider within Kubernetes itself. There you should make a pull request I think.
Describe the solution you'd like I would like to choose Trident as a Storage Class provider via the UI of Rancher and not configure it under the hood and choose "local" as a provider.
Describe alternatives you've considered The alternative is to install Trident manually but i think it's not an enterprise integration.
Additional context Other already available providers are Amazon EBS Disk, Azure Disk, Azure File, Ceph RBD, Gluster Volume, Google Persistent Disk, Local Storage, Longhorn, Openstack Cinder Volume, Portworx Volume, Quobyte Volume, ScaleIO Volume, StorageOS, VMWare vSphere Volume.