dosc: vCluster -> vcluster & chart.devspace.sh

Author: FabianKramm

docs/pages/fragments/install/on-premise.mdx

@@ -87,7 +87,7 @@ Cert Manager will automatically provision SSL certificates for your ingress host
 #### Install Loft to management cluster via helm v3
 
 ```bash
-helm install loft loft --repo https://charts.devspace.sh/ \
+helm install loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --create-namespace \
   --set admin.username=admin \              # Username for your (admin) user
@@ -142,7 +142,7 @@ helm install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ing
 #### Install Loft via Helm v3
 
 ```bash
-helm install loft loft --repo https://charts.devspace.sh/ \
+helm install loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --create-namespace \
   --set admin.username=admin \

docs/pages/fragments/vclusters/create.mdx

@@ -26,9 +26,9 @@ Run this command to create a virtual cluster:
 loft create vcluster [VCLUSTER_NAME]   # optional flag: --cluster=[CLUSTER_NAME]
 ```
 
-Creating a virtual cluster using the CLI will automatically configure a kube-context on your local machine for this vCluster.
+Creating a virtual cluster using the CLI will automatically configure a kube-context on your local machine for this vcluster.
 
-With the kube-context of the vCluster, you can run any kubectl command within the virtual cluster:
+With the kube-context of the vcluster, you can run any kubectl command within the virtual cluster:
 ```bash
 kubectl get namespaces
 ```

docs/pages/getting-started/setup.mdx

@@ -133,7 +133,7 @@ helm install cert-manager cert-manager --repo https://charts.jetstack.io \
 
 **Upgrade your Loft instance via Helm:**
 ```bash {5}
-helm upgrade loft loft --repo https://charts.devspace.sh/ \
+helm upgrade loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --reuse-values \
   --set certIssuer.create=true \

docs/pages/guides/administration/air-gapped-installation.mdx

@@ -91,7 +91,7 @@ export REGISTRY=my-private-registry:5000
 
 # Run the helm command
 helm install loft loft --repository-config '' \
-   --repo https://charts.devspace.sh \
+   --repo https://charts.loft.sh \
    --version $VERSION \
    --set admin.password=$PASSWORD \
    --set admin.email=$EMAIL \
@@ -124,7 +124,7 @@ export LICENSE=LICENSE_KEY
 
 # Run the helm command
 helm install loft loft --repository-config '' \
-    --repo https://charts.devspace.sh \
+    --repo https://charts.loft.sh \
     --version $VERSION \
     --set admin.password=$PASSWORD \
     --set admin.email=$EMAIL \
@@ -180,7 +180,7 @@ export REGISTRY=my-private-registry:5000
 
 # Run the helm command
 helm upgrade loft loft --repository-config '' \
-   --repo https://charts.devspace.sh \
+   --repo https://charts.loft.sh \
    --version $VERSION \
    --namespace loft \
    --reuse-values \
@@ -197,7 +197,7 @@ export VERSION=1.13.0
 
 # Run the helm command
 helm upgrade loft loft --repository-config '' \
-    --repo https://charts.devspace.sh \
+    --repo https://charts.loft.sh \
     --version $VERSION \
     --namespace loft
 ```

docs/pages/guides/administration/high-availability.mdx

@@ -14,7 +14,7 @@ By default, loft will run in a cluster as a single replica without high availabi
 To configure loft to be highly available, you only have to set the environment variable `LEADER_ELECTION_ENABLED` to `true` on the loft deployment. Then you can then scale up the replicas and loft will start with leader election mode. You can do that via helm on an existing loft installation:
 ```
 # Run loft with 3 replicas
-helm upgrade loft loft --repo https://charts.devspace.sh/ \
+helm upgrade loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --reuse-values \
   --set-string env.LEADER_ELECTION_ENABLED=true \

docs/pages/guides/administration/metrics.mdx

@@ -11,7 +11,7 @@ The metrics can be scraped with the included `ServiceMonitor` in the loft chart,
 
 ```bash
 # Make sure you change serviceMonitor.namespace if your prometheus installation requires this.
-helm upgrade loft loft --repo https://charts.devspace.sh/ \
+helm upgrade loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --reuse-values \
   --set serviceMonitor.enabled=true \

docs/pages/guides/administration/self-signed-certificate.mdx

@@ -76,7 +76,7 @@ kubectl create secret generic my-loft-cert -n loft --type=kubernetes.io/tls --fr
 
 Now the only thing left to do is to tell loft to use tls instead of expecting the ingress controller to handle this. This can be done via helm:
 ```
-helm upgrade loft loft --repo https://charts.devspace.sh/ \
+helm upgrade loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --reuse-values \
   --set tls.enabled=true \

docs/pages/guides/administration/upgrade.mdx

@@ -5,7 +5,7 @@ sidebar_label: Upgrade Loft
 
 Make sure you are in the kube-context of your Loft management cluster and run the following command using helm v3:
 ```bash
-helm upgrade -n loft loft loft --repo https://charts.devspace.sh --reuse-values --version 0.0.1
+helm upgrade -n loft loft loft --repo https://charts.loft.sh --reuse-values --version 0.0.1
 ```
 
 :::important Version Numbers

docs/pages/guides/onboarding.mdx

@@ -118,13 +118,13 @@ kubectl get po
 
 ## Virtual Clusters
 
-### Create vCluster
+### Create Virtual Cluster
 <CreateVClusterFragment/>
 
-### Use vCluster
+### Use Virtual Cluster
 <UseVClusterFragment/>
 
-### Delete vCluster
+### Delete Virtual Cluster
 <DeleteVClusterFragment/>
 
 ## Quotas

docs/pages/multi-tenancy/apps.mdx

@@ -67,7 +67,7 @@ curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-
 
 Import `loft` and label it as system app:
 ```bash
-curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-release.sh" | bash -s -- "loft" "https://charts.devspace.sh" true false
+curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-release.sh" | bash -s -- "loft" "https://charts.loft.sh" true false
 ```
 :::
 

docs/pages/multi-tenancy/shared-secrets.mdx

@@ -345,7 +345,7 @@ This is an enterprise feature. Please make sure your license permits secrets enc
 By default, secrets are **not** encrypted and stored plain text (base64 encoded) in the underlying shared secrets custom resource. You can configure loft to encrypt the data of secrets by specifying an encryption key. This can be done via helm:
 
 ```
-helm upgrade loft loft --repo https://charts.devspace.sh/ \
+helm upgrade loft loft --repo https://charts.loft.sh/ \
   --namespace loft \
   --reuse-values \
   --set env.SECRETS_ENCRYPTION_KEY=my-secret-encryption-key

docs/pages/quickstart.mdx

@@ -172,21 +172,21 @@ While users can use `kubectl` or any localhost UI (e.g. [Lens](https://github.co
 
 
 #### How to work with virtual clusters?
-Using virtual clusters (vClusters) is very similar to using spaces:
+Using virtual clusters is very similar to using spaces:
 
 <Tabs
   defaultValue="create"
   values={[
-    { label: 'Create vClusters', value: 'create', },
-    { label: 'Delete vClusters', value: 'delete', },
-    { label: 'List vClusters', value: 'list', },
-    { label: 'Use vClusters', value: 'use', },
-    { label: 'Inspect vClusters', value: 'inspect', },
+    { label: 'Create Virtual Clusters', value: 'create', },
+    { label: 'Delete Virtual Clusters', value: 'delete', },
+    { label: 'List Virtual Clusters', value: 'list', },
+    { label: 'Use Virtual Clusters', value: 'use', },
+    { label: 'Inspect Virtual Clusters', value: 'inspect', },
   ]
 }>
 <TabItem value="create">
 
-While users will be able to create vClusters via the UI, it is much easier to create them via the CLI:
+While users will be able to create Virtual Clusters via the UI, it is much easier to create them via the CLI:
 ```bash
 loft create vcluster my-dev-stack-1
 ```
@@ -202,7 +202,7 @@ kubectl create namespace backend  # create a namespace `backend`
 kubectl get pods -n kube-system   # list 
 ```
 
-:::note vCluster Admin
+:::note Virtual Cluster Admin
 Especially looking at the last example command above, you can see that the user really is admin of this virtual cluster. Although the user only has very restricted access to a single namespace of the host cluster, the user is admin of the virtual cluster that runs inside this namespace of the host cluster.
 :::
 
@@ -244,7 +244,7 @@ While users can use `kubectl` or any localhost UI (e.g. [Lens](https://github.co
 </figure>
 
 :::note Cross-Namespace Views
-All vCluster inspection views you can see in the Loft UI are essentially using the `kubectl --all-namespaces` flag because virtual clusters tend to have a much smaller amount of namespaces and resources than regular clusters, so it is very fast to show all resources across all namespaces.
+All virtual cluster inspection views you can see in the Loft UI are essentially using the `kubectl --all-namespaces` flag because virtual clusters tend to have a much smaller amount of namespaces and resources than regular clusters, so it is very fast to show all resources across all namespaces.
 :::
 
 </TabItem>
@@ -256,7 +256,7 @@ Sometimes, your engineers may need more than just namespaces, e.g. when:
 - they deploy applications to multiple namespaces (e.g. database is supposed to run in a different namespace)
 - they want to install something that needs to add Custom Resource Definitions
 
-In such cases, users can create virtual clusters (vClusters) instead of spaces/namespaces. Learn more about [virtual Kubernetes clusters](https://loft.sh/blog/introduction-into-virtual-clusters-in-kubernetes/).
+In such cases, users can create virtual clusters instead of spaces/namespaces. Learn more about [virtual Kubernetes clusters](https://loft.sh/blog/introduction-into-virtual-clusters-in-kubernetes/).
 
 
 ### 3.3 Sleep Mode + Auto-Delete

docs/pages/self-service/virtual-clusters.mdx

@@ -1,5 +1,5 @@
 ---
-title: Virtual Clusters (vClusters)
+title: Virtual Clusters
 sidebar_label: Virtual Clusters
 ---
 
@@ -24,13 +24,13 @@ Virtual clusters:
 
 ## Workflows
 
-### Create vCluster
+### Create Virtual Cluster
 <CreateVClusterFragment/>
 
-### Use vCluster
+### Use Virtual Cluster
 <UseVClusterFragment/>
 
-### Delete vCluster
+### Delete Virtual Cluster
 <DeleteVClusterFragment/>
 
 <br/>
@@ -58,7 +58,7 @@ syncer:
 
 ### Overriding vcluster defaults
 
-There are default values how a new virtual cluster will be deployed by Loft either through the UI (vClusters > Create vCluster) or through the Loft CLI (`loft create vcluster`). These default values can be overridden on cluster level by setting the annotation `virtualcluster.loft.sh/default-values` to the new values. 
+There are default values how a new virtual cluster will be deployed by Loft either through the UI (Virtual Clusters > Create Virtual Cluster) or through the Loft CLI (`loft create vcluster`). These default values can be overridden on cluster level by setting the annotation `virtualcluster.loft.sh/default-values` to the new values. 
 
 For example, if you want to disable ingress syncing by default, you would use this as default values:
 ```yaml
@@ -75,8 +75,8 @@ syncer:
 You can now navigate to Clusters > Show Yaml and set the annotation accordingly.
 
 <figure class="frame">
-    <img src="/docs/media/ui/vclusters/vcluster-default-values.png" alt="vCluster Set Default Values" />
-    <figcaption>vCluster Set Default Values</figcaption>
+    <img src="/docs/media/ui/vclusters/vcluster-default-values.png" alt="vcluster Set Default Values" />
+    <figcaption>vcluster Set Default Values</figcaption>
 </figure>
 
 The next time a new virtual cluster is created through the Loft CLI or UI in this connected cluster these new default values will be applied.
@@ -92,8 +92,8 @@ A virtual Kubernetes cluster in Loft is tied to a single namespace. The virtual
 - an instance of a virtual cluster hypervisor which is mainly responsible for syncing cluster resources between the k3s powered virtual cluster and the underlying host cluster
 
 <figure class="frame">
-  <img src="/docs/media/ui/vclusters/vcluster-architecture.png" alt="vCluster Architecture" />
-  <figcaption>vCluster Architecture Overview</figcaption>
+  <img src="/docs/media/ui/vclusters/vcluster-architecture.png" alt="Virtual Cluster Architecture" />
+  <figcaption>Virtual Cluster Architecture Overview</figcaption>
 </figure>
 
 ### Host Namespace

hack/import-helm-release.sh

@@ -17,7 +17,7 @@ if [ "$1" = "" ] || [ "$2" = "" ]; then
   echo 'curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-release.sh" | bash -s -- "ingress-nginx" "https://kubernetes.github.io/ingress-nginx"'
   echo ""
   echo 'Example 3:'
-  echo 'curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-release.sh" | bash -s -- "loft" "https://charts.devspace.sh" true false'
+  echo 'curl -L "https://raw.githubusercontent.com/loft-sh/loft/master/hack/import-helm-release.sh" | bash -s -- "loft" "https://charts.loft.sh" true false'
   exit 1
 fi