fix truenas scale vm guide (#30401)

**Description**
<!--
Please include a summary of the change and which issue is fixed. Please
also include relevant motivation and context. List any dependencies that
are required for this change.
-->
⚒️ Fixes  # <!--(issue)-->

**⚙️ Type of change**

- [ ] ⚙️ Feature/App addition
- [ ] 🪛 Bugfix
- [ ] ⚠️ Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 🔃 Refactor of current code

**🧪 How Has This Been Tested?**
<!--
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
-->

**📃 Notes:**
<!-- Please enter any other relevant information here -->

**✔️ Checklist:**

- [ ] ⚖️ My code follows the style guidelines of this project
- [ ] 👀 I have performed a self-review of my own code
- [ ] #️⃣ I have commented my code, particularly in hard-to-understand
areas
- [ ] 📄 I have made corresponding changes to the documentation
- [ ] ⚠️ My changes generate no new warnings
- [ ] 🧪 I have added tests to this description that prove my fix is
effective or that my feature works
- [ ] ⬆️ I increased versions for any altered app according to semantic
versioning
- [ ] I made sure the title starts with `feat(chart-name):`,
`fix(chart-name):` or `chore(chart-name):`

** App addition**

If this PR is an app addition please make sure you have done the
following.

- [ ] 🖼️ I have added an icon in the Chart's root directory called
`icon.png`

---

_Please don't blindly check all the boxes. Read them and only check
those that apply.
Those checkboxes are there for the reviewer to see what is this all
about and
the status of this PR with a quick glance._

Signed-off-by: alfi0812 <43101280+alfi0812@users.noreply.github.com>
This commit is contained in:
alfi0812
2024-12-28 09:33:30 -05:00
committed by GitHub
parent cc0c4cd2b7
commit 3c770c03f8
@@ -246,59 +246,14 @@ Below you can find 2 examples on how to set a fixed DHCP Lease for UniFi and Fri
![DHCP FritzBox](./img/dhcp_fritzbox.png) ![DHCP FritzBox](./img/dhcp_fritzbox.png)
(screenshot in german) (screenshot in german)
## TalConfig Examples ## Post-Installation steps
Here are a few examples you can copy-paste into talconfig to setup the above VMs to run Talos.
### Single-Node Cluster or Master-Node
By default we ensure qemu guest additions are always loaded for all master-nodes.
It's important to note that for master nodes, we use static IPs for referencing them *after* they are initially initialised using a Fixed DHCP lease.
```yaml
- hostname: k8s-control-1
ipAddress: ${MASTER1IP}
controlPlane: true
nameservers:
- 8.8.8.8
- 1.1.1.1
installDiskSelector:
size: <= 100TB
networkInterfaces:
- interface: eth0
addresses:
- ${MASTER1IP}/24
routes:
- network: 0.0.0.0/0
gateway: ${GATEWAY}
vip:
ip: ${VIP}
```
### Worker Node
By default we ensure qemu guest additions are always loaded for all worker-nodes.
Workernodes can be pretty basic and should "just work".
```yaml
- hostname: k8s-worker-1
ipAddress: 192.168.10.111
nameservers:
- 8.8.8.8
- 1.1.1.1
installDiskSelector:
size: <= 600GB
```
### Post-Installation steps
To make sure your Talos cluster starts correctly after restarting the VM, don't forget to remove the Installation Media ISO after you initialized the cluster. To make sure your Talos cluster starts correctly after restarting the VM, don't forget to remove the Installation Media ISO after you initialized the cluster.
You can do this by going to `Virtualization` > Expand your VM > `Devices` and then delete the "CD Rom"-device. You can do this by going to `Virtualization` > Expand your VM > `Devices` and then delete the "CD Rom"-device.
### GPU pass-through Caveats ## GPU pass-through Caveats
Users running the Talos VM atop a TrueNAS SCALE host system that want to also take advantage of GPU passthrough to the VM will require a **minimum** of 2 *different* GPUs to be present in the system. Users running the Talos VM atop a TrueNAS SCALE host system that want to also take advantage of GPU passthrough to the VM will require a **minimum** of 2 *different* GPUs to be present in the system.
@@ -317,7 +272,7 @@ or
**GPU2:** Intel iGPU or dedicated Nvidia GPU isolated within SCALE for VM passthrough **GPU2:** Intel iGPU or dedicated Nvidia GPU isolated within SCALE for VM passthrough
### Single GPU pass-through (Advanced) ## Single GPU pass-through (Advanced)
:::caution[Work In Progress] :::caution[Work In Progress]