Omni Documentation
Try OmniTalos Linux
  • Omni Documentation
  • Omni Support Matrix
  • Tutorials
    • Getting Started with Omni
    • Upgrading Omni Clusters
    • Installing Airgapped Omni
    • Using SAML and ACLs for fine-grained access control
    • Setting Up the Bare-Metal Infrastructure Provider
  • How-to guides
    • Using SAML with Omni
      • Add a User to Omni with SAML Enabled
      • Auto-assign roles to SAML users
      • Configure Workspace ONE Access for Omni
      • Configure Okta for Omni
      • Configure Entra ID AD for Omni
      • Configure Unifi Identity Enterprise for Omni
    • Register machines with Omni
      • Register a Bare Metal Machine (ISO)
      • Register a Bare Metal Machine (PXE/iPXE)
      • Register an AWS EC2 Instance
      • Register an Azure Instance
      • Register a GCP Instance
      • Register a Hetzner Server
    • Create a Cluster
    • Install talosctl
    • Install and Configure Omnictl
    • Use Kubectl With Omni
    • Create a Kubeconfig for a Kubernetes Service Account
    • Create a Patch For Cluster Machines
    • Manage Access Policies (ACLs)
    • Create a Hybrid Cluster
    • Run Omni on your own infrastructure
      • Deploy Omni On-prem
      • Configure Keycloak for Omni
      • Back Up On-prem Omni Database
      • How to expose Omni with Nginx (HTTPS)
    • Install Talos Linux Extensions
    • Scale a Cluster Up or Down
    • Etcd backups
    • Restore Etcd of a Cluster Managed by Cluster Templates
    • Create an Omni Service Account
    • Create a Machine Class
    • Expose an HTTP Service from a Cluster
    • Export a Cluster Template from a Cluster Created in the UI
    • Audit logs
    • Set Initial Machine Labels Using Omnictl or Image Factory
  • Explanation
    • Machine Registration
    • Authentication and Authorization
    • Omni KMS Disk Encryption
    • Infrastructure Providers
  • Reference
    • omnictl CLI
    • Access Policies (ACLs)
    • Generating omnictl CLI reference
    • Cluster Templates
Powered by GitBook
On this page
Edit on GitHub
Export as PDF
  1. How-to guides

Register machines with Omni

PreviousConfigure Unifi Identity Enterprise for OmniNextRegister a Bare Metal Machine (ISO)

Last updated 7 days ago

The first step to creating and managing Kubernetes clusters in Omni is registering the machines you wish to use. The machines can run anywhere Talos Linux runs. The guides in this section walk you through the specifics of different platforms.

In general, the process to register a machine with Omni consists of downloading the installation media from your Omni account, and booting the machine off that media.

To start the process, from the Home screen, click "Download Installation Media" on the right hand side:

The Download Installation Media form will open:

This allows you to select media specific to various platforms (AWS, Azure, bare metal, etc), and also to specify options, such as:

  • the versions of Talos Linux to initially boot with (note that it is recommended to have all machines that will form a cluster be at the same Talos Linux version.)

  • optional extensions to be bundled into the image (providing support for additional features, such as GPUs, driver microcode, etc.)

  • specific machine labels to be applied to the machines booted off this image (useful for identifying machines by racks, or location, etc)

  • optional capabilities such as:

  • Generating iPXE boot URLs: if your machines can boot via iPXE, you can configure them to boot directly off Omni via the Image Factory integration. Simply click to generate the PXE Boot URL, and pass that in to your systems to boot from.

Note that some platforms have other specific requirements, which can be seen in the articles within this section.

SecureBoot (which verifies the signatures of the operating system, ensuring only trusted code is executed). For more information see the page.

Tunneling Omni management WireGuard traffic over HTTP2, via the SideroLink gRPC connection. Normally Omni management traffic runs over UDP. In some environments, that may not be possible. Running the Omni management traffic over HTTP (via gRPC) may allow operation in such restricted environments, but at a cost of substantial overhead. See the page for more information.

Talos Linux SecureBoot
Talos Linux SideroLink