You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@joaocc sorry for the delay, vcluster has problems with EFS as its causing issues with databases in general, do you have any chance to use EBS or something similar?
Hi. Not really. We are using EFS as a way to simplify HA storage.
Contrary to Azure, where ZRS allows mountable volumes that cross different AZs, it seems AWS EBS is restricted to a single AZ, so a vcluster that ends up being booted on another node would not be able to mount the EBS.
On the other hand, we haven't noticed any kind of practical issues. Are you saying that EFS is not a supported storage for etcd?
Thanks
we use eks-d because the remaining distros use sqlite which is indeed not able to be hosted on NFS-type file systems; do you think the new k3s-with-etcd at v0.19.x will have the same issues?
regarding EBS, is there any guidance to have non-HA deployments work well with EBS on multi-AZ clusters (in the case a single AZ becomes unavailable) - this is a scenario that is supported quite well with EFS.
is there any official statement on EFS being a supported store with etcd?
For reference, we continue not to have any practical issues, except for a elevated EFS billing account (writes ~440MB/sec), which we are still trying to understand if it is from these writes or from something else.
What happened?
Installed vcluster-eks 0.16.4 on EKS 1.27. Storage for etcd is on EFS.
Messages start almost immediately after vcluster-api pod starts
What did you expect to happen?
No warning messages
How can we reproduce it (as minimally and precisely as possible)?
Not sure how to reproduce in minimal environment.
Anything else we need to know?
Install done via flux2 (HelmRelease)
Potentially relevant links:
Host cluster Kubernetes version
Host cluster Kubernetes distribution
vlcuster version
Vcluster Kubernetes distribution(k3s(default)), k8s, k0s)
OS and Arch
The text was updated successfully, but these errors were encountered: