Synced Resources
This section lists all resources that can be synced or mirrored by vCluster currently in the table below. Those resources can be activated or deactivated via the values.yaml as described below, or with the --sync flag of the syncer. By default, certain resources are already activated and you can either disable the default resources or tell vCluster to sync other supported resources as well.
| Resource | Description | Default Enabled |
|---|---|---|
| services | Mirrors services between host and virtual cluster | Yes |
| endpoints | Mirrors endpoints between host and virtual cluster | Yes |
| configmaps | Mirrors used configmaps by pods between host and virtual cluster | Yes |
| secrets | Mirrors used secrets by ingresses or pods between host and virtual cluster | Yes |
| events | Syncs events from host cluster to virtual cluster | Yes |
| pods | Mirrors pods between host and virtual cluster | Yes |
| persistentvolumeclaims | Mirrors persistent volume claims between host and virtual cluster | Yes |
| fake-nodes | Creates fake nodes based on spec.nodeName fields of synced pods. Requires no cluster role | Yes |
| fake-persistentvolumes | Creates fake persistent volumes based on spec.volumeName of persistent volume claims. Requires no cluster role | Yes |
| ingresses | Mirrors ingresses between host and virtual cluster. Automatically tries to detect the supported ingress version (networking.k8s.io/v1 or networking.k8s.io/v1beta1) | No |
| ingressclasses | Syncs IngressClasses from host cluster to virtual cluster. This is automatically enabled when Ingresses sync is enabled. | No * |
| nodes | Syncs real nodes from host cluster to virtual cluster. If enabled, implies that fake-nodes is disabled. For more information see nodes. | No |
| persistentvolumes | Mirrors persistent volumes from vCluster to host cluster and dynamically created persistent volumes from host cluster to virtual cluster. If enabled, implies that fake-persistentvolumes is disabled. For more information see storage. | No |
| storageclasses | Syncs created storage classes from virtual cluster to host cluster | No |
| hoststorageclasses | Syncs real storage classes from host cluster to virtual cluster. This is only needed if you require to be able to get/list StorageClasses from vCluster API server. Host storage classes can be used in PersistentVolumes and PersistentVolumeClaims without syncing them to the virtual cluster. This option was formerly named "legacy-storageclasses". | No |
| priorityclasses | Syncs created priority classes from virtual cluster to host cluster | No |
| networkpolicies | Syncs created network policies from virtual cluster to host cluster | No |
| volumesnapshots | Enables volumesnapshot, volumesnapshotcontents and volumesnapshotclasses support. Syncing behaves similar to persistentvolumeclaims, persistentvolumes and storage classes. For more information see storage. | No |
| poddisruptionbudgets | Syncs created poddisruptionbudgets from virtual cluster to host cluster | No |
| serviceaccounts | Syncs created service accounts from virtual cluster to host cluster. This is useful for using IAM roles for service accounts with vCluster | No |
| csidrivers | Mirrors CSIDriver objects from host cluster to vCluster. Enabled automatically when virtual scheduler is enabled. Disabling this syncer while using virtual scheduler may result in incorrect pod scheduling. | No * |
| csinodes | Mirrors CSINode objects from host cluster to vCluster. Enabled automatically when virtual scheduler is enabled. Disabling this syncer while using virtual scheduler may result in incorrect pod scheduling. | No * |
| csistoragecapacities | Mirrors CSIStorageCapacity Objects from host cluster to vCluster if the .nodeTopology matches a synced node. Enabled automatically when virtual scheduler is enabled. Disabling this syncer while using virtual scheduler may result in incorrect pod scheduling. | No * |
* refer to the description column for clarifying information about default behavior.
By default, vCluster runs with a minimal set of RBAC permissions to allow execution in restricted environments. Certain resources require extra permissions, which will be automatically given to the vCluster ServiceAccount if you enable the resource sync with the associated helm value