mirrors/sidero
1
0
Fork 0
mirror of https://github.com/siderolabs/sidero.git synced 2026-05-05 20:36:29 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix clusterctl usage

Browse Source 
Fix clusterctl usage

Signed-off-by: Noel Georgi <git@frezbo.dev>
This commit is contained in:
Noel Georgi 2021-11-30 12:39:58 +05:30
parent e77bf54a31
commit 5bf7c21f8f
No known key found for this signature in database
GPG Key ID: B1F736354201D483
6 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/content/docs/v0.4/Getting Started/create-workload.md
View File

@ -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

4
website/content/docs/v0.4/Guides/bootstrapping.md
View File

@ -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:
@ -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.

2
website/content/docs/v0.4/Guides/first-cluster.md
View File

@ -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:

2
website/content/docs/v0.5/Getting Started/create-workload.md
View File

@ -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

4
website/content/docs/v0.5/Guides/bootstrapping.md
View File

@ -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:
@ -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.

2
website/content/docs/v0.5/Guides/first-cluster.md
View File

@ -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: