From 82c516975990bc537d5b6a0baa3178b96687b276 Mon Sep 17 00:00:00 2001 From: heiko-braun Date: Mon, 18 Mar 2024 11:20:49 +0100 Subject: [PATCH 1/2] Point docs to v0.19 branch --- .../pages/architecture/control_plane/k8s_distros.mdx | 6 +++--- docs/pages/deploying-vclusters/high-availability.mdx | 4 ++-- docs/pages/deploying-vclusters/supported-distros.mdx | 12 ++++++------ docs/pages/fragments/high-availability-k3s.mdx | 2 +- docs/pages/fragments/high-availability-k8s.mdx | 2 +- 5 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/pages/architecture/control_plane/k8s_distros.mdx b/docs/pages/architecture/control_plane/k8s_distros.mdx index 6a4eb67f4..67e49d795 100644 --- a/docs/pages/architecture/control_plane/k8s_distros.mdx +++ b/docs/pages/architecture/control_plane/k8s_distros.mdx @@ -24,7 +24,7 @@ kubectl get ns ... ``` -Behind the scenes, a different helm chart will be deployed (`vcluster-k0s`), that holds specific configurations to support k0s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/main/charts/k0s) for all available chart options. +Behind the scenes, a different helm chart will be deployed (`vcluster-k0s`), that holds specific configurations to support k0s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k0s) for all available chart options. ## Vanilla k8s @@ -42,7 +42,7 @@ 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/main/charts/k8s) for all available chart options. +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. ## Other Distributions @@ -73,6 +73,6 @@ vCluster only needs the following information from the virtual Kubernetes distri 2. The API server central authority key (usually found at `/pki/ca.key`) 3. An admin kube config to contact the virtual Kubernetes control plane (usually found at `/pki/admin.conf`) -For multi-binary distributions, vCluster can even create those with a pre-install hook as found in the [k8s chart](https://github.com/loft-sh/vcluster/tree/main/charts/k8s/templates). +For multi-binary distributions, vCluster can even create those with a pre-install hook as found in the [k8s chart](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k8s/templates). In general, if you need vCluster to support another Kubernetes distribution, we are always happy to help you or accept a pull request in our GitHub repository. diff --git a/docs/pages/deploying-vclusters/high-availability.mdx b/docs/pages/deploying-vclusters/high-availability.mdx index 7f4e469aa..362bc3de2 100644 --- a/docs/pages/deploying-vclusters/high-availability.mdx +++ b/docs/pages/deploying-vclusters/high-availability.mdx @@ -207,7 +207,7 @@ kubectl get ns ``` -Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/main/charts/k3s) for all available chart options. +Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k3s) for all available chart options. ### Enabling High Availability with Vanilla k8s @@ -311,4 +311,4 @@ coredns: type: RuntimeDefault ``` -Check the [github repository](https://github.com/loft-sh/vcluster/tree/main/charts/k8s) for all available chart options. +Check the [github repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k8s) for all available chart options. diff --git a/docs/pages/deploying-vclusters/supported-distros.mdx b/docs/pages/deploying-vclusters/supported-distros.mdx index 09779ab8e..16d7b97b6 100644 --- a/docs/pages/deploying-vclusters/supported-distros.mdx +++ b/docs/pages/deploying-vclusters/supported-distros.mdx @@ -21,7 +21,7 @@ kubectl get ns ... ``` -Behind the scenes the default helm chart will be deployed, which holds a specific configuration to support k3s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/main/charts/k3s) for all available chart options. +Behind the scenes the default helm chart will be deployed, which holds a specific configuration to support k3s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k3s) for all available chart options. ## k0s @@ -39,7 +39,7 @@ kubectl get ns ... ``` -Behind the scenes a different helm chart will be deployed (`vcluster-k0s`), that holds specific configuration to support k0s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/main/charts/k0s) for all available chart options. +Behind the scenes a different helm chart will be deployed (`vcluster-k0s`), that holds specific configuration to support k0s. Check the [github repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k0s) for all available chart options. Please note that dual stack networking is not supported with k0s, you will be able to deploy it on a dual stack host cluster, but it will not have all the dual stack features. @@ -59,7 +59,7 @@ 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/main/charts/k8s) for all available chart options. +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 @@ -78,7 +78,7 @@ 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/main/charts/eks) for all available chart options. +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 @@ -104,13 +104,13 @@ And then deploy vCluster with: vcluster create my-vcluster -n test --distro k8s -f values.yaml ``` -If you want to create a separate chart for the Kubernetes distribution, a good starting point is to copy one of [our distro charts](https://github.com/loft-sh/vcluster/tree/main/charts) and then modify it to work with your distribution. +If you want to create a separate chart for the Kubernetes distribution, a good starting point is to copy one of [our distro charts](https://github.com/loft-sh/vcluster/tree/v0.19/charts) and then modify it to work with your distribution. vCluster only needs the following information from the virtual Kubernetes distribution to function properly: 1. The api server central authority certificate (usually found at `/pki/ca.crt`) 2. The api server central authority key (usually found at `/pki/ca.key`) 3. An admin kube config to contact the virtual Kubernetes control plane (usually found at `/pki/admin.conf`) -For multi binary distributions, vCluster can even create those with a pre-install hook as found in the [k8s chart](https://github.com/loft-sh/vcluster/tree/main/charts/k8s/templates). +For multi binary distributions, vCluster can even create those with a pre-install hook as found in the [k8s chart](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k8s/templates). In general, if you need vCluster to support another Kubernetes distribution, we are always happy to help you or accept a pull request in our GitHub repository. diff --git a/docs/pages/fragments/high-availability-k3s.mdx b/docs/pages/fragments/high-availability-k3s.mdx index 01972578e..8b1c6171e 100644 --- a/docs/pages/fragments/high-availability-k3s.mdx +++ b/docs/pages/fragments/high-availability-k3s.mdx @@ -56,4 +56,4 @@ kubectl get ns ``` -Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/main/charts/k3s) for all available chart options. +Check the [GitHub repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k3s) for all available chart options. diff --git a/docs/pages/fragments/high-availability-k8s.mdx b/docs/pages/fragments/high-availability-k8s.mdx index 81820c2d2..5dcf88506 100644 --- a/docs/pages/fragments/high-availability-k8s.mdx +++ b/docs/pages/fragments/high-availability-k8s.mdx @@ -99,4 +99,4 @@ coredns: type: RuntimeDefault ``` -Check the [github repository](https://github.com/loft-sh/vcluster/tree/main/charts/k8s) for all available chart options. +Check the [github repository](https://github.com/loft-sh/vcluster/tree/v0.19/charts/k8s) for all available chart options. From 3ff25496c3e4d2a501870200ad7c4478ada8dfe9 Mon Sep 17 00:00:00 2001 From: Johannes Frey Date: Thu, 4 Apr 2024 08:55:56 +0200 Subject: [PATCH 2/2] Reference helm charts for v0.19 --- docs/pages/architecture/control_plane/k8s_distros.mdx | 2 +- docs/pages/getting-started/deployment.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/pages/architecture/control_plane/k8s_distros.mdx b/docs/pages/architecture/control_plane/k8s_distros.mdx index 67e49d795..e282bcb2c 100644 --- a/docs/pages/architecture/control_plane/k8s_distros.mdx +++ b/docs/pages/architecture/control_plane/k8s_distros.mdx @@ -67,7 +67,7 @@ And then deploy vCluster with: vcluster create my-vcluster -n test --distro k8s -f values.yaml ``` -If you want to create a separate chart for the Kubernetes distribution, a good starting point is to copy one of [our distro charts](https://github.com/loft-sh/vcluster/tree/main/charts) and then modify it to work with your distribution. +If you want to create a separate chart for the Kubernetes distribution, a good starting point is to copy one of [our distro charts](https://github.com/loft-sh/vcluster/tree/v0.19/charts) and then modify it to work with your distribution. vCluster only needs the following information from the virtual Kubernetes distribution to function properly: 1. The API server central authority certificate (usually found at `/pki/ca.crt`) 2. The API server central authority key (usually found at `/pki/ca.key`) diff --git a/docs/pages/getting-started/deployment.mdx b/docs/pages/getting-started/deployment.mdx index 8922346ce..9c027cec1 100644 --- a/docs/pages/getting-started/deployment.mdx +++ b/docs/pages/getting-started/deployment.mdx @@ -113,5 +113,5 @@ This tells vCluster to prepend the image registry to all images used by vCluster You can find a list of all needed images by vCluster in the file `vcluster-images.txt` at the [releases page](https://github.com/loft-sh/vcluster/releases), as well as two scripts (download-images.sh & push-images.sh) to pull and push those to your private registry. -You can locate the Helm chart and values file for Kubernetes distro in the vCluster [repo](https://github.com/loft-sh/vcluster/tree/main/charts). Be sure to choose the tag that matches your vCluster version. +You can locate the Helm chart and values file for Kubernetes distro in the vCluster [repo](https://github.com/loft-sh/vcluster/tree/v0.19/charts). Be sure to choose the tag that matches your vCluster version.