Create a VM Migration Assistant Profile
Follow these steps to create a new add-on profile that will be applied to your existing VMO cluster.
Prerequisites
-
Your Palette account role must have the
clusterProfile.createpermission to create a cluster profile. Refer to the Permissions documentation for more information. -
A healthy VMO cluster. Refer to the Create a VMO Profile for further guidance.
- The VMO cluster must have network connectivity to vCenter and ESXi hosts, and the VMs you want to migrate.
-
If you using an Ubuntu 24.04 pack as your OS layer, such as Ubuntu 24.04 for MaaS, you must set
kernel.apparmor_restrict_unprivileged_userns=0in the/etc/sysctl.d/10-kubernetes-tuning.conffile through the OS layer configuration in the cluster profile to ensure that the configuration persists after node restarts.This is required to allow the VM Migration Assistant to perform disk or image conversions without running into permission issues related to unprivileged user namespaces.
How to add the kernel parameter to your cluster profile
-
Log in to Palette.
-
From the left main menu, select Profiles.
-
Find and select the cluster profile linked to your VMO cluster.
-
Create a new version of the cluster profile. Refer to the Version Cluster Profile documentation for guidance on creating a new version of your cluster profile.
-
In the new version of your cluster profile, select the OS layer to view the Edit Pack page.
-
Under Pack Details, select Values to view the YAML code editor.
-
Add the kernel parameter to the
kubeadmconfig.filessection. The following is an example YAML snippet to demonstrate how to add the parameter.Examplekubeadmconfig:
files:
- targetPath: /etc/sysctl.d/10-kubernetes-tuning.conf
targetOwner: "root:root"
targetPermissions: "0644"
content: |-
kernel.apparmor_restrict_unprivileged_userns=0If your cluster profile already has a configuration for the
10-kubernetes-tuning.conffile, add thekernel.apparmor_restrict_unprivileged_userns=0line to the existing content while ensuring proper YAML formatting. -
Click Confirm Updates to save the changes to the OS layer configuration.
-
On the cluster profile page, click Save Changes.
-
Use the cluster profile to deploy a new cluster or update an existing cluster.
-
-
If your OS pack or node image uses containerd v2, you must set
device_ownership_from_security_context = truein the/etc/containerd/conf.d/device-ownership.tomlfile using the Kubernetes layer of your cluster profile to ensure that the configuration persists after node restarts.Enable this setting so non-root Container Device Interface (CDI) pods can access block devices during block-volume transfer operations. Since containerd v2, this parameter is opt-in and must be set to true.
How to add the device ownership parameter to your cluster profile
-
Log in to Palette.
-
From the left main menu, select Profiles.
-
Find and select the cluster profile linked to your VMO cluster.
-
Create a new version of the cluster profile. Refer to the Version Cluster Profile documentation for guidance on creating a new version of your cluster profile.
-
In the new version of your cluster profile, select the Kubernetes layer to view the Edit Pack page.
-
Under Pack Details, select Values to view the YAML code editor.
-
Add the device ownership parameter to the
kubeadmconfig.filessection. The following is an example YAML snippet to demonstrate how to add the parameter.Examplekubeadmconfig:
files:
- targetPath: /etc/containerd/conf.d/device-ownership.toml
targetOwner: "root:root"
targetPermissions: "0644"
content: |
[plugins."io.containerd.grpc.v1.cri"]
device_ownership_from_security_context = trueIf your cluster profile already has a configuration for the
device-ownership.tomlfile, add the entry withincontentto the existing content while ensuring proper YAML formatting. -
Click Confirm Updates to save the changes to the OS layer configuration.
-
On the cluster profile page, click Save Changes.
-
Use the cluster profile to deploy a new cluster or update an existing cluster.
-
Create the Profile
-
Log in to Palette.
-
From the left main menu, click Profiles.
-
Click on the Add Cluster Profile button.
-
Fill out the basic information and ensure you select Add-on for the type. Click on Next to continue.
-
Select Add New Pack. In the next window that displays, enter Virtual Machine Migration Assistant in the Filter by name search bar. The pack is in the Public Repo registry. Select the pack when it appears.
-
Palette displays the YAML file in the editor on the right. You can edit the YAML as needed. Review the following service console parameters and adjust to your requirements as needed.
Parameter Description Default Value vm-migration-assistant-ui.console.service.typeChoose how to expose the service console: NodePort/LoadBalancer/ClusterIP. Refer to Service type for guidance on Kubernetes service types."LoadBalancer"vm-migration-assistant-ui.console.service.loadBalancerPortChoose the external port to expose the service console when LoadBalancer is selected. "443"vm-migration-assistant-ui.console.service.nodePortChoose the external port to expose the service console when nodePortis selected."30443"vm-migration-assistant-ui.console.deployment.env.userAuthIf you want to enable OIDC for the service console, set the value to oidc. The OIDC configuration is inherited from your Kubernetes pack configuration. The service console supports OIDC with Palette as the Identity Provider (IdP), or with a Custom third-party OIDC IdP, such as Okta or Azure Active Directory. If you use a Custom IdP, you must also configure the IdP redirect URI and refresh token. Refer to Configure Custom OIDC for VM Migration Assistant for those steps, and to SAML and OIDC SSO for details on Palette OIDC.disabledvm-migration-assistant-ui.console.ingress.enabledChoose whether to enable Ingress access to the VM Migration Assistant service console. If enabled, the Ingress provides external connectivity to the service console. You can still access the service console through the cluster services list in Palette if vm-migration-assistant-ui.console.service.typeis set toLoadBalancerorNodePort.falsevm-migration-assistant-ui.console.ingress.hostSpecify the domain name that the Ingress resource will use to expose the VM Migration Assistant service console. vm-migration-assistant-ui.console.ingress.tlsIf providing your own TLS certificates, define the TLS configuration for the Ingress within this parameter. If you need to secure multiple domains or subdomains with different certificates, you can add multiple entries. Each array must contain the secretName,hosts,crt, andkeyparameters.vm-migration-assistant-ui.console.ingress.tls.secretNameThe name for the Kubernetes Secret where the TLS certificate and key will be stored. vm-migration-assistant-ui.console.ingress.tls.hostsOne or more hostnames that the certificate should secure. vm-migration-assistant-ui.console.ingress.tls.crtThe CA-issued TLS certificate. vm-migration-assistant-ui.console.ingress.tls.keyThe private key corresponding to the certificate. vm-migration-assistant-ui.console.ingress.selfSignedIssuer.enabledWhen set to true, cert-manager will automatically issue a self-signed TLS certificate based on theingress.tls.hostsandingress.tls.secretNamevalues. This allows you to omit the manual certificate and key parameters beingingress.tls.crtandingress.tls.keyrespectively.false -
Click on Confirm & Create.
-
In the following screen, click Next.
-
Click Finish Configuration.
-
From the left main menu, select Clusters and select your VMO cluster.
-
In the Profile tab, click Add add-on profile (+) and select the newly created profile. Click Confirm.
-
Click Save to deploy the VM Migration Assistant to your cluster.
Validate
-
Log in to Palette.
-
From the left main menu, select Profiles.
-
Locate the newly created profile in the list.
-
From the left main menu, click Clusters and select your cluster.
-
In the Overview tab, ensure that the cluster status and health is Running and Healthy.
-
In the Overview tab, the Services list displays the vm-migration service with a clickable port. Click the port to access the VM Migration Assistant service console. The port number is based on your service console configuration.
Access the VM Migration Assistant Service Console
You can access the service console based on how you configured the VM Migration Assistant YAML manifest when creating the cluster profile.
The following examples are for each console.service.type:
-
If you configured an
Ingresswith adomainofvm-migration.mycompany.dev, you can access the service console athttps://vm-migration.mycompany.dev. -
If you configured a
NodePortwith anodePortof30443, you can access the service console athttps://<NODE_IP>:30443.
- If you configured a
LoadBalancerwith aloadBalancerPortof443, you can access the service console athttps://<LOAD_BALANCER_IP>, where the load balancer IP address is provided by your load balancer solution (such as MetalLB).
Next Steps
You can now use the VM Migration Assistant to migrate your VMs. Refer to the Create Source Providers guide to start creating your source providers.