Skip to content

Commit 2df0c49

Browse files
[v0.30] Makes standalone component page a link instead of half install instru… (#1344) (#1346)
* Backport: Copy vcluster/_fragments/standalone.mdx to vcluster_versioned_docs/version-0.30.0/_fragments/standalone.mdx * Backport: Copy vcluster/configure/vcluster-yaml/control-plane/components/standalone.mdx to vcluster_versioned_docs/version-0.30.0/configure/vcluster-yaml/control-plane/components/standalone.mdx * Backport: Copy vcluster/deploy/control-plane/binary/README.mdx to vcluster_versioned_docs/version-0.30.0/deploy/control-plane/binary/README.mdx --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent 2985c63 commit 2df0c49

File tree

3 files changed

+12
-25
lines changed

3 files changed

+12
-25
lines changed

vcluster_versioned_docs/version-0.30.0/_fragments/standalone.mdx

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -14,13 +14,3 @@ nodes must be private nodes.
1414
alt="vCluster Standalone Architecture"
1515
/>
1616
</center>
17-
18-
## Installation overview
19-
20-
vCluster Standalone requires having dedicated nodes to build your control plane nodes and optionally add additional worker nodes.
21-
22-
The steps are to bring up a vCluster Standalone cluster are:
23-
24-
1. Install an initial control plane node.
25-
2. (Optional) Join additional control plane nodes.
26-
3. (Optional) Join worker nodes.

vcluster_versioned_docs/version-0.30.0/configure/vcluster-yaml/control-plane/components/standalone.mdx

Lines changed: 2 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -14,20 +14,7 @@ import TenancySupport from '../../../../_fragments/tenancy-support.mdx';
1414

1515
<Standalone />
1616

17-
## Node Roles
17+
For more information see the full [Standalone Documentation](../../../../deploy/control-plane/binary/)
1818

19-
By default, the node only acts as a control plane node, but can be enabled to run as a
20-
worker node as well.
21-
22-
```yaml title="Allow control plane node to be a worker node"
23-
controlPlane:
24-
standalone:
25-
enabled: true
26-
joinNode:
27-
enabled: true # Control Plane node will also be considered a worker node
28-
privateNodes: # Required when adding additional worker nodes
29-
enabled: true
30-
```
31-
32-
## Config Reference
19+
## Config reference
3320
<StandaloneConfig />

vcluster_versioned_docs/version-0.30.0/deploy/control-plane/binary/README.mdx

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,16 @@ import TenancySupport from '../../../_fragments/tenancy-support.mdx';
1414

1515
<Standalone />
1616

17+
## Installation overview
18+
19+
vCluster Standalone requires having dedicated nodes to build your control plane nodes and optionally add additional worker nodes.
20+
21+
The steps are to bring up a vCluster Standalone cluster are:
22+
23+
1. Install an initial control plane node.
24+
2. (Optional) Join additional control plane nodes.
25+
3. (Optional) Join worker nodes.
26+
1727
## vcluster.yaml configuration
1828

1929
To create a vCluster Standalone with one node that is the control plane and worker node. Read more about [high availability](./high-availability).

0 commit comments

Comments
 (0)