Skip to content

docs: add documentation about QEMU presets #75

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add documentation about QEMU presets #75

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions public/talos/v1.12/platform-specific-installations/local-platforms/qemu.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading