Stay organized with collections Save and categorize content based on your preferences.

Configuring a processing cluster on Anthos on bare metal

This topic describes how to set up Anthos on bare metal clusters as a processing cluster for migrating Linux VMs. You use the processing cluster to generate migrated container artifacts, operate, and monitor the migration.

Before you begin

Before creating Anthos on bare metal clusters, you need:

  • A user with GKE Administrator privileges. These privileges are only necessary for the setup portion.
  • A Google service account, with the necessary permissions, to install Migrate to Containers components. See Configuring a service account for more.

Distinctions from Anthos clusters on VMware

The setup process between Anthos on bare metal clusters and Anthos clusters on VMware is similar, however, the functionality between the two differs.

  • Anthos clusters on VMware - Google Kubernetes Engine (GKE) runs in your data center in a vSphere environment. vSphere is VMware's server virtualization software. Anthos clusters on VMware uses VMware's vCenter Server to manage your clusters.

  • Anthos on bare metal clusters - Anthos on bare metal clusters lets you deploy applications directly on your own hardware infrastructure to deliver the best performance and flexibility. While you are using your own hardware and network, you have direct control over application scale, security, and network latency, as well as having the benefit of containerized applications through Google Kubernetes Engine (GKE) and Anthos components.

Both cluster types perform their migrations on-prem and the source is always VMware, but the resulting workloads are deployed in the environment of their processing cluster.

Creating a processing cluster

Because of the many options you have when installing Anthos on bare metal, see Creating a user cluster in the Anthos on bare metal documentation.

Your cluster must:

  • Run Anthos on bare metal clusters
  • Define at least one node with 4 or more CPUs and 15 GB or more of RAM
  • Define a default storage class that supports creation of Persistent Volumes with volumeMode of both Filesystem and Block.

Using a private cluster

Private clusters give you the ability to isolate nodes from having inbound and outbound connectivity to the public internet. This isolation is achieved as the nodes have internal IP addresses only.

Migrate to Containers supports the use of private clusters. When using a private cluster, the control plane node must be able to reach the Migrate to Containers infrastructure pod on port 9443.

Therefore, you must ensure that port 9443 is accessible to the control plane node.

What's next