diff --git a/docs/pages/deploying-vclusters/high-availability.mdx b/docs/pages/deploying-vclusters/high-availability.mdx index 362bc3de27..32335a350a 100644 --- a/docs/pages/deploying-vclusters/high-availability.mdx +++ b/docs/pages/deploying-vclusters/high-availability.mdx @@ -19,12 +19,16 @@ brew install loft-sh/tap/vcluster For other platforms, see [the installation instructions](../getting-started/setup.mdx). # 2. Understanding vCluster distros -A distro in vcluster is the Kubernetes distribution that runs inside the virtual cluster. There are four supported distros at the time of this writing: +A distro in vcluster is the Kubernetes distribution that runs inside the virtual cluster. These are the supported distributions: - k3s (the default distro) - k0s -- eks (the Kubernetes that is installed in AWS EKS clusters) - k8s (a Kubernetes with etcd) +- eks (the Kubernetes that is installed in AWS EKS clusters) + +:::warning EKS Distribution +Though the EKS distribution is supported in v0.19, it is deprecated. Reminder: The Kubernetes distribution of the virtual cluster doesn't need to match the the distribution of your host cluster. You can use any distribution of vCluster to deploy vCluster on EKS clusters. +::: For this tutorial, we will use the k8s distro. If you're interested in enabling HA in rootless mode, or using the k3s distro, see some examples at the bottom of this page. diff --git a/docs/pages/deploying-vclusters/supported-distros.mdx b/docs/pages/deploying-vclusters/supported-distros.mdx index f3fe00a903..e9de53bf79 100644 --- a/docs/pages/deploying-vclusters/supported-distros.mdx +++ b/docs/pages/deploying-vclusters/supported-distros.mdx @@ -64,6 +64,26 @@ kubectl get ns Behind the scenes, a different helm chart will be deployed (`vcluster-k8s`), that holds specific configuration to support vanilla k8s. Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k8s) for all available chart options. +## eks + +:::warning EKS Distribution +Though the EKS distribution is supported in v0.19, it is deprecated. Reminder: The Kubernetes distribution of the virtual cluster doesn't need to match the the distribution of your host cluster. You can use any distribution of vCluster to deploy vCluster on EKS clusters. +::: + +When choosing this option, vCluster will deploy a separate etcd cluster. + +In order to use eks as backing cluster, create a vCluster with the following command: + +``` +vcluster create my-vcluster --distro eks +``` + +Connect to the vCluster and start using it: +``` +kubectl get ns +... +``` + Behind the scenes, a different helm chart will be deployed (`vcluster-eks`), that holds a specific configuration to support vanilla k8s. Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/eks) for all available chart options. ## Other Distributions diff --git a/docs/pages/help&tutorials/helm-provisioning.mdx b/docs/pages/help&tutorials/helm-provisioning.mdx index cfbea53cce..cf99929c35 100644 --- a/docs/pages/help&tutorials/helm-provisioning.mdx +++ b/docs/pages/help&tutorials/helm-provisioning.mdx @@ -155,6 +155,10 @@ We can see the complete list of values that can be modified and their default se If you’re not familiar with what a vCluster distro is, the distro is the distribution of Kubernetes that runs inside of the virtual cluster. The default is k3s, and the other supported distros are k0s, eks, and k8s (a larger Kubernetes install that uses etcd). +:::warning EKS Distribution +Though the EKS distribution is supported in v0.19, it is deprecated. Reminder: The Kubernetes distribution of the virtual cluster doesn't need to match the the distribution of your host cluster. You can use any distribution of vCluster to deploy vCluster on EKS clusters. +::: + We’ve used the default distro for this tutorial, k3s. To view its default values, we’d want to examine the file vcluster/charts/k3s/values.yaml. You can view the [entire file here](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k3s/values.yaml). diff --git a/docs/pages/what-are-virtual-clusters.mdx b/docs/pages/what-are-virtual-clusters.mdx index d52f9a03db..850c310024 100644 --- a/docs/pages/what-are-virtual-clusters.mdx +++ b/docs/pages/what-are-virtual-clusters.mdx @@ -59,7 +59,7 @@ vClusters provide immense benefits for large-scale Kubernetes deployments and mu - Auto-scale, purge, snapshot, and move your vClusters, since they are Kubernetes deployments. - **Low Overhead:** - vClusters are super lightweight and only reside in a single namespace. - - vClusters run with [K3s](https://k3s.io/), a super low-footprint K8s distribution. You can use other [supported distributions](./deploying-vclusters/supported-distros) such as [K0s](https://k0sproject.io/), vanilla [Kubernetes](https://kubernetes.io/), and [AWS EKS](https://aws.amazon.com/eks/). + - vClusters run with [K3s](https://k3s.io/), a super low-footprint K8s distribution. You can use other [supported distributions](./deploying-vclusters/supported-distros) such as [K0s](https://k0sproject.io/) or vanilla [Kubernetes](https://kubernetes.io/). [AWS EKS](https://aws.amazon.com/eks/) is a supported distribution that is now deprecated. - The vCluster control plane runs inside a single pod. Open source vCluster also uses a CoreDNS pod for vCluster-internal DNS capabilities. With vCluster.Pro, however, you can [enable the integrated CoreDNS](https://www.vcluster.com/pro/docs/features/integrated_coredns) so you don't need the additional pod. - **No Network Degradation:** - Since the pods and services inside a vCluster are actually being synchronized down to the host cluster, they are effectively using the underlying cluster's pod and service networking. The vCluster pods are as fast as other pods in the underlying host cluster.