From 5a4620b4bc11aa24db835ec5a331a90395d2d1e8 Mon Sep 17 00:00:00 2001 From: Orzelius Date: Sat, 18 Oct 2025 10:39:23 +0900 Subject: [PATCH] docs: add documentation about QEMU presets and omni endpoint flag Signed-off-by: Orzelius <33936483+Orzelius@users.noreply.github.com> --- .../local-platforms/qemu.mdx | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/public/talos/v1.12/platform-specific-installations/local-platforms/qemu.mdx b/public/talos/v1.12/platform-specific-installations/local-platforms/qemu.mdx index 186ee55..08f3d50 100644 --- a/public/talos/v1.12/platform-specific-installations/local-platforms/qemu.mdx +++ b/public/talos/v1.12/platform-specific-installations/local-platforms/qemu.mdx @@ -91,10 +91,21 @@ On Linux, before the first cluster is created, `talosctl` will download the CNI Once the above finishes successfully, your talosconfig (`~/.talos/config`) will be configured to point to the new cluster, and `kubeconfig` will be downloaded and merged into default kubectl config location (`~/.kube/config`). +### Presets + +The `talosctl cluster create qemu` command has various presets available via the `--presets` flag to modify behavior. +See [reference documentation](../../reference/cli#talosctl-cluster-create-qemu") for more details. + ### Image factory schematic Optionally a custom [Image Factory](../../getting-started/talosctl) schematic ID can be provided via the `--schematic-id` flag. +### Omni + +The `omni-api-endpoint` flag configures nodes to connect to an Omni instance once booted. +Using [SideroLink](../../networking/siderolink), the local QEMU nodes can communicate with Omni as long as the endpoint is reachable. +This enables connections to a local Omni instance, a cloud-hosted Omni instance, or a Sidero SaaS Omni instance. + ## Using the Cluster Once the cluster is available, you can make use of `talosctl` and `kubectl` to interact with the cluster.