abdelouahabb opened a new pull request #198:
URL: https://github.com/apache/cloudstack-documentation/pull/198
1- to not confuse new comers who have AMD
2- If they are missing someone cant run an instance
Issue : https://github.com/apache/cloudstack/issues/4810
So based on your message those storages should be available to containers
on some kind of protocols over network, NFS for instance.
I thought that we can attach a virtual disk to the VM that hosts the pod,
and then directly attach it to the pod. In case of pod migration, we can
detach the disk and
DaanHoogland commented on a change in pull request #79:
URL: https://github.com/apache/cloudstack-www/pull/79#discussion_r593773050
##
File path: content/contribute.html
##
@@ -145,7 +145,7 @@ Apache CloudStack: Getting Involved
Developers, of course, are also welcome. See
Maybe I am wrong but I think it’s a better way and make it more easier to use
the storage interface in Kubernetes but make it configurable over CS. I don’t
see the pro to integrate this over CS because it needs many maintenance over
the time if we know that things can change.
I think a better
yeah, it is good to support multiple CNI plugins, weavenet(default for
now), flannel, calico, etc.
-Wei
On Fri, 12 Mar 2021 at 21:32, Sven Vogel wrote:
> Hi Wei,
>
>
> >>CloudStack kubernetes clusters should use other storage (for example
> NFS or
> ceph) for persistent volumes.
>
>
> if i not
Thanks Alireza.
It is a long list. Almost all drivers in the list are for block storage
solutions or file shares. containers can access the resources directly.
Different to them, cloudstack volumes are attached to VMs, not to pods or
containers. containers cannot attach cloudstack volumes. All
