Skip to content

Commit

Permalink
docs: fix clusterctl usage
Browse files Browse the repository at this point in the history
Fix clusterctl usage

Signed-off-by: Noel Georgi <git@frezbo.dev>
  • Loading branch information
frezbo committed Nov 30, 2021
1 parent e77bf54 commit 5bf7c21
Show file tree
Hide file tree
Showing 6 changed files with 8 additions and 8 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ export KUBERNETES_VERSION=v1.22.2
export CONTROL_PLANE_PORT=6443
export CONTROL_PLANE_ENDPOINT=1.2.3.4

clusterctl config cluster cluster-0 -i sidero > cluster-0.yaml
clusterctl generate cluster cluster-0 -i sidero > cluster-0.yaml
```

Take a look at this new `cluster-0.yaml` manifest and make any changes as you
Expand Down
4 changes: 2 additions & 2 deletions website/content/docs/v0.4/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ We are now ready to template out our management plane.
Using clusterctl, we can create a cluster manifest with:
```bash
clusterctl config cluster management-plane -i sidero > management-plane.yaml
clusterctl generate cluster management-plane -i sidero > management-plane.yaml
```
Note that there are several variables that should be set in order for the templating to work properly:
Expand Down Expand Up @@ -235,7 +235,7 @@ export TALOS_VERSION=v0.13
export KUBERNETES_VERSION=v1.22.2
export CONTROL_PLANE_PORT=6443
export CONTROL_PLANE_ENDPOINT=1.2.3.4
clusterctl config cluster management-plane -i sidero > management-plane.yaml
clusterctl generate cluster management-plane -i sidero > management-plane.yaml
```
In addition, you can specify the replicas for control-plane & worker nodes in management-plane.yaml manifest for TalosControlPlane and MachineDeployment objects.
Expand Down
2 changes: 1 addition & 1 deletion website/content/docs/v0.4/Guides/first-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -107,7 +107,7 @@ The cluster creation process should be identical to what was detailed in the pre
Using clusterctl, we can create a cluster manifest with:
```bash
clusterctl config cluster workload-cluster -i sidero > workload-cluster.yaml
clusterctl generate cluster workload-cluster -i sidero > workload-cluster.yaml
```
Note that there are several variables that should be set in order for the templating to work properly:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ export KUBERNETES_VERSION=v1.22.2
export CONTROL_PLANE_PORT=6443
export CONTROL_PLANE_ENDPOINT=1.2.3.4

clusterctl config cluster cluster-0 -i sidero > cluster-0.yaml
clusterctl generate cluster cluster-0 -i sidero > cluster-0.yaml
```

Take a look at this new `cluster-0.yaml` manifest and make any changes as you
Expand Down
4 changes: 2 additions & 2 deletions website/content/docs/v0.5/Guides/bootstrapping.md
Original file line number Diff line number Diff line change
Expand Up @@ -207,7 +207,7 @@ We are now ready to template out our management plane.
Using clusterctl, we can create a cluster manifest with:
```bash
clusterctl config cluster management-plane -i sidero > management-plane.yaml
clusterctl generate cluster management-plane -i sidero > management-plane.yaml
```
Note that there are several variables that should be set in order for the templating to work properly:
Expand Down Expand Up @@ -235,7 +235,7 @@ export TALOS_VERSION=v0.13
export KUBERNETES_VERSION=v1.22.2
export CONTROL_PLANE_PORT=6443
export CONTROL_PLANE_ENDPOINT=1.2.3.4
clusterctl config cluster management-plane -i sidero > management-plane.yaml
clusterctl generate cluster management-plane -i sidero > management-plane.yaml
```
In addition, you can specify the replicas for control-plane & worker nodes in management-plane.yaml manifest for TalosControlPlane and MachineDeployment objects.
Expand Down
2 changes: 1 addition & 1 deletion website/content/docs/v0.5/Guides/first-cluster.md
Original file line number Diff line number Diff line change
Expand Up @@ -115,7 +115,7 @@ The cluster creation process should be identical to what was detailed in the pre
Using clusterctl, we can create a cluster manifest with:
```bash
clusterctl config cluster workload-cluster -i sidero > workload-cluster.yaml
clusterctl generate cluster workload-cluster -i sidero > workload-cluster.yaml
```
Note that there are several variables that should be set in order for the templating to work properly:
Expand Down

0 comments on commit 5bf7c21

Please sign in to comment.