docs(doc-1334): terminology — remaining vcluster sections batch 5

Replace "virtual cluster(s)" with "tenant cluster(s)" and "host cluster"
with "control plane cluster" across key-features, understand, configure,
deploy, integrations, learn-how-to, reference, troubleshoot, and _fragments
sections. Fixes broken anchor in architecture.mdx referencing
replicate-services after prior heading rename.

Part of DOC-1334

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: djwfyi

vcluster/_fragments/default-distro-note.mdx

@@ -1,3 +1,3 @@
 :::info
-vCluster uses Kubernetes as the default distribution for the virtual cluster.
+vCluster uses Kubernetes as the default distribution for the tenant cluster.
 :::

vcluster/_fragments/delete-vcluster.mdx

@@ -2,7 +2,7 @@ import Tabs from '@theme/Tabs'
 import TabItem from '@theme/TabItem'
 
 :::caution Resources inside vCluster
-Deleting a vCluster instance also deletes all objects within and all states related to the vCluster. If the namespace on the host cluster was created by the vCluster CLI, then that namespace is also deleted. 
+Deleting a vCluster instance also deletes all objects within and all states related to the vCluster. If the namespace on the control plane cluster was created by the vCluster CLI, then that namespace is also deleted. 
 :::
 
 <Tabs
@@ -33,7 +33,7 @@ helm delete my-vcluster -n vcluster-my-vcluster --repository-config=''
 </TabItem>
 <TabItem value="kubectl">
 
-The easiest option to delete a virtual cluster using `kubectl` is to delete the host namespace:
+The easiest option to delete a tenant cluster using `kubectl` is to delete the host namespace:
 ```bash
 kubectl delete namespace vcluster-my-vcluster
 ```

vcluster/_fragments/deploy/backing-store.mdx

@@ -48,7 +48,7 @@ controlPlane:
 <TabItem value="embedded-sqlite-nopv">
 
 By default, vCluster stores its data in a `PersistentVolumeClaim` (PVC).
-Alternatively, you can use an [`emptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) volume to store virtual cluster data.
+Alternatively, you can use an [`emptyDir`](https://kubernetes.io/docs/concepts/storage/volumes/#emptydir) volume to store tenant cluster data.
 
 To use an `emptyDir` to store the data instead of a `PersistentVolume`, create a `values.yaml` with the following contents:
 

vcluster/_fragments/deploy/control-plane.mdx

@@ -5,6 +5,6 @@ import BackingStoreYAMLOptions from './backing-store.mdx'
 Decide the various options of how you want your control plane deployed:
 
 - **[High availability](./high-availability)** - Run multiple copies of vCluster components.
-- **[Rootless mode](./security/rootless-mode)** - Deploy the vCluster pod without root access to the host cluster.
+- **[Rootless mode](./security/rootless-mode)** - Deploy the vCluster pod without root access to the control plane cluster.
 - **Backing Store** - Decide how the data of your cluster is stored.
    <BackingStoreYAMLOptions />

vcluster/_fragments/deploy/nested/control-plane.mdx

@@ -5,6 +5,6 @@ import BackingStoreYAMLOptions from '../backing-store.mdx'
 Decide the various options of how you want your control plane deployed:
 
 - **[High availability](./../high-availability)** - Run multiple copies of vCluster components.
-- **[Rootless mode](./../security/rootless-mode)** - Deploy the vCluster pod without root access to the host cluster.
+- **[Rootless mode](./../security/rootless-mode)** - Deploy the vCluster pod without root access to the control plane cluster.
 - **Backing Store** - Decide how the data of your cluster is stored.
   <BackingStoreYAMLOptions />

vcluster/_fragments/deploy/nested/worker-nodes.mdx

@@ -2,7 +2,7 @@
 
 Decide where you want your worker nodes to come from:
 
-- **[Nodes from the host cluster](../../../worker-nodes/host-nodes)** - (Default) All worker nodes of the shared host cluster are used by the virtual cluster and all resources are synced to the single namespace that the vCluster is deployed on.
-  - **[Syncing Namespaces](../../../../configure/vcluster-yaml/sync/from-host/nodes)** - Resources are synced to mapped namespaces on the host cluster.
+- **[Nodes from the control plane cluster](../../../worker-nodes/host-nodes)** - (Default) All worker nodes of the shared control plane cluster are used by the tenant cluster and all resources are synced to the single namespace that the vCluster is deployed on.
+  - **[Syncing Namespaces](../../../../configure/vcluster-yaml/sync/from-host/nodes)** - Resources are synced to mapped namespaces on the control plane cluster.
   - **[Isolated workloads](../../../worker-nodes/host-nodes/isolated-workloads)** - Different options to isolate a workload in a vCluster.
-- **[Private Nodes](../../../worker-nodes/private-nodes)** - Enable adding individual nodes to the virtual cluster.
+- **[Private Nodes](../../../worker-nodes/private-nodes)** - Enable adding individual nodes to the tenant cluster.

vcluster/_fragments/deploy/worker-nodes.mdx

@@ -3,7 +3,7 @@
 
 Decide where you want your worker nodes to come from:
 
-- **[Nodes from the host cluster](../../worker-nodes/host-nodes)** - (Default) All worker nodes of the shared host cluster are used by the virtual cluster and all resources are synced to the single namespace that the vCluster is deployed on.
-  - **[Syncing Namespaces](../../../configure/vcluster-yaml/sync/from-host/nodes)** - Resources are synced to mapped namespaces on the host cluster.
+- **[Nodes from the control plane cluster](../../worker-nodes/host-nodes)** - (Default) All worker nodes of the shared control plane cluster are used by the tenant cluster and all resources are synced to the single namespace that the vCluster is deployed on.
+  - **[Syncing Namespaces](../../../configure/vcluster-yaml/sync/from-host/nodes)** - Resources are synced to mapped namespaces on the control plane cluster.
   - **[Isolated workloads](../../worker-nodes/host-nodes/isolated-workloads)** - Different options to isolate a workload in a vCluster.
-- **[Private Nodes](../../worker-nodes/private-nodes)** - Enable adding individual nodes to the virtual cluster.
+- **[Private Nodes](../../worker-nodes/private-nodes)** - Enable adding individual nodes to the tenant cluster.

vcluster/_fragments/distro/compat-k0s.mdx

@@ -1,8 +1,8 @@
 import KubernetesVersions from '../../_partials/deploy/kubernetes-versions.mdx'
 import { HostClusterCompat } from '../../_partials/deploy/host-cluster-compat.mdx'
 
-### Host cluster compatibility
+### Control plane cluster compatibility
 <HostClusterCompat distro="k0s"/>
 
-vCluster should work when deployed on a host cluster with the following supported Kubernetes versions:
+vCluster should work when deployed on a control plane cluster with the following supported Kubernetes versions:
 <KubernetesVersions/>

vcluster/_fragments/distro/compat-k3s.mdx

@@ -1,9 +1,9 @@
 import KubernetesVersions from '../../_partials/deploy/kubernetes-versions.mdx'
 import { HostClusterCompat } from '../../_partials/deploy/host-cluster-compat.mdx'
 
-### Host cluster compatibility
+### Control plane cluster compatibility
 <HostClusterCompat distro="k3s"/>
 
-vCluster should work when deployed on a host cluster with the following supported Kubernetes versions:
+vCluster should work when deployed on a control plane cluster with the following supported Kubernetes versions:
 <KubernetesVersions/>
 

vcluster/_fragments/distro/compat-k8s.mdx

@@ -1,6 +1,6 @@
 import { HostClusterCompat } from '../../_partials/deploy/host-cluster-compat.mdx'
 
-### Host cluster compatibility
+### Control plane cluster compatibility
 <HostClusterCompat distro="k8s"/>
 
-vCluster supports specific Kubernetes versions on host clusters. For more information, see the [Kubernetes compatibility matrix](../../manage/upgrade/supported_versions.mdx#kubernetes-compatibility-matrix).
+vCluster supports specific Kubernetes versions on control plane clusters. For more information, see the [Kubernetes compatibility matrix](../../manage/upgrade/supported_versions.mdx#kubernetes-compatibility-matrix).