Skip to content

Commit

Permalink
Update nodes.mdx
Browse files Browse the repository at this point in the history
  • Loading branch information
@kmadel
kmadel authored Feb 21, 2025
1 parent 0b4cae7 commit a016202
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions vcluster/configure/vcluster-yaml/sync/from-host/nodes.mdx
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ import SyncNodes from '../../../../_partials/config/sync/fromHost/nodes.mdx'
{/*
`nodes.enabled`:
- covered by the generic section here: https://www.vcluster.com/docs/syncer/config#enable-or-disable-synced-resources
- exists from the beginning. I believe one would need this to schedule any pods
- exists from the beginning. This is needed to schedule any pods
- may be possible to disable this in the "control plane" vCluster when using [Isolated Control Plane](https://www.vcluster.com/pro/docs/features/isolated_control_planes), where all the workloads are scheduled to the workload cluster (where nodes syncing would be enabled)

Check warning on line 14 in vcluster/configure/vcluster-yaml/sync/from-host/nodes.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Google.WordList] Use 'turn off' or 'off' instead of 'disable'.

Raw Output:
{"message": "[Google.WordList] Use 'turn off' or 'off' instead of 'disable'.", "location": {"path": "vcluster/configure/vcluster-yaml/sync/from-host/nodes.mdx", "range": {"start": {"line": 14, "column": 22}}}, "severity": "WARNING"}
`nodes.syncBackChanges`:
Expand All @@ -26,12 +26,12 @@ import SyncNodes from '../../../../_partials/config/sync/fromHost/nodes.mdx'
- sets `--sync-all-nodes` syncer flag, see also [Example: Sync All Nodes](https://www.vcluster.com/docs/architecture/nodes#example-sync-all-nodes)
`nodes.selector.labels`:
- selects node labels that will be synced to the vCluster. This allows controlling which nodes can be used by the vCluste
- selects node labels that are synced to the vCluster. This allows controlling which nodes can be used by the vCluste
- Some example use cases:
- only allow nodes in a region
- only allow nodes with a particular architecture
- only use spot instances
- prevent vClusters from sharing resources with critical infrastructure
- prevent vCluster from sharing resources with critical infrastructure
*/}

By default, this is disabled.

Check warning on line 37 in vcluster/configure/vcluster-yaml/sync/from-host/nodes.mdx

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Google.WordList] Use 'turn off' or 'off' instead of 'disabled'.

Raw Output:
{"message": "[Google.WordList] Use 'turn off' or 'off' instead of 'disabled'.", "location": {"path": "vcluster/configure/vcluster-yaml/sync/from-host/nodes.mdx", "range": {"start": {"line": 37, "column": 21}}}, "severity": "WARNING"}
Expand All @@ -40,7 +40,7 @@ vCluster syncs psuedo nodes from the host cluster where there are virtual cluste

However, when you need to access specific node information, you can choose to sync real nodes from the host cluster to the virtual cluster. This requires a cluster role.

### Sync pseudo nodes (Default)
### Sync pseudo nodes (default)

Sync pseudo nodes to the virtual cluster. This default configuration does not require a cluster role.

Expand Down

0 comments on commit a016202

Please sign in to comment.