mirrors/talos
1
0
Fork 0
mirror of https://github.com/siderolabs/talos.git synced 2025-11-02 09:21:13 +01:00
Code Issues Packages Projects Releases Wiki Activity

docs: update vmware docs

Browse Source 
Update VMWare docs to use `@` syntax to load files

Signed-off-by: Noel Georgi <git@frezbo.dev>
This commit is contained in:
Noel Georgi 2022-04-11 16:22:21 +05:30
parent da0e638f04
commit c382cb8cd2
No known key found for this signature in database
GPG Key ID: B1F736354201D483
3 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
website/content/v1.0/virtualized-platforms/vmware.md
View File

@ -22,7 +22,7 @@ This can be done with the `talosctl gen config ...` command.
Take note that we will also use a JSON6902 patch when creating the configs so that the control plane nodes get some special information about the VIP we chose earlier, as well as a daemonset to install vmware tools on talos nodes. Take note that we will also use a JSON6902 patch when creating the configs so that the control plane nodes get some special information about the VIP we chose earlier, as well as a daemonset to install vmware tools on talos nodes.
First, download `the cp.patch` to your local machine and edit the VIP to match your chosen IP. First, download `the cp.patch` to your local machine and edit the VIP to match your chosen IP.
You can do this by issuing `https://raw.githubusercontent.com/siderolabs/talos/master/website/content/{{< version >}}/virtualized-platforms/vmware/cp.patch`. You can do this by issuing `https://raw.githubusercontent.com/siderolabs/talos/master/website/content/{{< version >}}/virtualized-platforms/vmware/cp.patch.yaml`.
It's contents should look like the following: It's contents should look like the following:
```yaml ```yaml
@ -43,14 +43,14 @@ It's contents should look like the following:
With the patch in hand, generate machine configs with: With the patch in hand, generate machine configs with:
```bash ```bash
$ talosctl gen config vmware-test https://<VIP>:<port> --config-patch-control-plane "$(yq r -j cp.patch)" $ talosctl gen config vmware-test https://<VIP>:<port> --config-patch-control-plane @cp.patch.yaml
created controlplane.yaml created controlplane.yaml
created worker.yaml created worker.yaml
created talosconfig created talosconfig
``` ```
At this point, you can modify the generated configs to your liking if needed. At this point, you can modify the generated configs to your liking if needed.
Optionally, you can specify additional patches by adding to the `cp.patch` file downloaded earlier, or create your own patch files. Optionally, you can specify additional patches by adding to the `cp.patch.yaml` file downloaded earlier, or create your own patch files.
### Validate the Configuration Files ### Validate the Configuration Files

0
website/content/v1.0/virtualized-platforms/vmware/cp.patch → website/content/v1.0/virtualized-platforms/vmware/cp.patch.yaml
View File

6
website/content/v1.1/virtualized-platforms/vmware.md
View File

@ -22,7 +22,7 @@ This can be done with the `talosctl gen config ...` command.
Take note that we will also use a JSON6902 patch when creating the configs so that the control plane nodes get some special information about the VIP we chose earlier, as well as a daemonset to install vmware tools on talos nodes. Take note that we will also use a JSON6902 patch when creating the configs so that the control plane nodes get some special information about the VIP we chose earlier, as well as a daemonset to install vmware tools on talos nodes.
First, download `the cp.patch` to your local machine and edit the VIP to match your chosen IP. First, download `the cp.patch` to your local machine and edit the VIP to match your chosen IP.
You can do this by issuing `https://raw.githubusercontent.com/siderolabs/talos/master/website/content/{{< version >}}/virtualized-platforms/vmware/cp.patch`. You can do this by issuing `https://raw.githubusercontent.com/siderolabs/talos/master/website/content/{{< version >}}/virtualized-platforms/vmware/cp.patch.yaml`.
It's contents should look like the following: It's contents should look like the following:
```yaml ```yaml
@ -43,14 +43,14 @@ It's contents should look like the following:
With the patch in hand, generate machine configs with: With the patch in hand, generate machine configs with:
```bash ```bash
$ talosctl gen config vmware-test https://<VIP>:<port> --config-patch-control-plane "$(yq r -j cp.patch)" $ talosctl gen config vmware-test https://<VIP>:<port> --config-patch-control-plane @cp.patch.yaml
created controlplane.yaml created controlplane.yaml
created worker.yaml created worker.yaml
created talosconfig created talosconfig
``` ```
At this point, you can modify the generated configs to your liking if needed. At this point, you can modify the generated configs to your liking if needed.
Optionally, you can specify additional patches by adding to the `cp.patch` file downloaded earlier, or create your own patch files. Optionally, you can specify additional patches by adding to the `cp.patch.yaml` file downloaded earlier, or create your own patch files.
### Validate the Configuration Files ### Validate the Configuration Files