In that case, I think this driver is pretty good!

On Tue, 24 May 2022 at 20:26, Ricardo Pertuz <[email protected]>
wrote:

> We will try it to modify it to be more generic, I mean, have an Kubernetes
> cluster and have Cloudstack as the storage backend.
>
> BR,
>
> Ricardo
>
> On 18/05/22, 11:21 PM, "Rudraksh Kulshreshtha"
> <[email protected]> wrote:
>
>     Hey Ricardo,
>
>     While I haven't yet had a chance to use this in production, I've
> tested it
>     a lot. It works quite well in both KVM and VMware setups - even though
> the
>     docs do mention it only works with KVM. I'd ordinarily recommend you
> should
>     go ahead and use it, except the repo hasn't seen a lot of action in the
>     last few months. However - if your cluster's outside CloudStack, this
>     driver definitely won't work for you - it does depend on the underlying
>     nodes being provisioned by CloudStack. If your cluster's going to stay
>     outside CloudStack, perhaps I'd recommend going in for something like
> Rook
>     <https://rook.io/> or Longhorn <https://longhorn.io/>?
>
>     On Thu, May 19, 2022 at 2:33 AM Ricardo Pertuz <
> [email protected]>
>     wrote:
>
>     > Hi,
>     >
>     > Currently I have a Kubernetes cluster outside Cloudstack and I want
> to use
>     > this CSI to provision volumes with this driver:
>     > https://github.com/apalia/cloudstack-csi-driver, is it recommended?
> Is
>     > the an official one I can rather use?
>     >
>     > BR,
>     >
>     > Ricardo
>     >
>
>
>     --
>
>     Best!
>
>
>     Rudraksh Mukta Kulshreshtha
>
>     Vice-President - DevOps | Training | R&D
>
>     *IndiQus Technologies*
>
>     *O*  +91 11 4055 1411  |  *M* +91 99589 54879
>
>     indiqus.com <http://www.indiqus.com>
>
>
>     *This message is intended only for the use of the individual or entity
> to
>     which it is addressed and may contain information that is confidential
>     and/or privileged. If you are not the intended recipient please delete
> the
>     original message and any copy of it from your computer system. You are
>     hereby notified that any dissemination, distribution or copying of this
>     communication is strictly prohibited unless proper authorization has
> been
>     obtained for such action. If you have received this communication in
> error,
>     please notify the sender immediately. Although IndiQus attempts to
> sweep
>     e-mail and attachments for viruses, it does not guarantee that both are
>     virus-free and accepts no liability for any damage sustained as a
> result of
>     viruses.*
>
>     --
>     This message is intended only for the use of the individual or entity
> to
>     which it is addressed and may contain confidential and/or privileged
>     information. If you are not the intended recipient, please delete the
>     original message and any copy of it from your computer system. You are
>     hereby notified that any dissemination, distribution or copying of
> this
>     communication is strictly prohibited unless proper authorization has
> been
>     obtained for such action. If you have received this communication in
> error,
>     please notify the sender immediately. Although IndiQus attempts to
> sweep
>     e-mail and attachments for viruses, it does not guarantee that both
> are
>     virus-free and accepts no liability for any damage sustained as a
> result of
>     viruses.
>
> --
Best,

Rudraksh MK
VP - R&D
IndiQus
e: [email protected]
m: +91-9958954879

-- 
This message is intended only for the use of the individual or entity to 
which it is addressed and may contain confidential and/or privileged 
information. If you are not the intended recipient, please delete the 
original message and any copy of it from your computer system. You are 
hereby notified that any dissemination, distribution or copying of this 
communication is strictly prohibited unless proper authorization has been 
obtained for such action. If you have received this communication in error, 
please notify the sender immediately. Although IndiQus attempts to sweep 
e-mail and attachments for viruses, it does not guarantee that both are 
virus-free and accepts no liability for any damage sustained as a result of 
viruses.

Reply via email to