The information contained in this page and its subsections applies to you when you have decided to migrate your first-gen pod using the Single Virtual Machine type of Horizon Edge Gateway deployment.
The information here assumes that you have read the section Decide on Your Deployment Type and Fulfill Its Requirements, answered the questions, and decided to use the Single Virtual Machine deployment type for the pod's migration.
For most environments, when you fulfill the prerequisites described in the sections of page Prerequisites for Migrating a First-Gen Horizon Cloud Pod, you have fulfilled the requirements for this type of deployment. Please see that page and its sections for the requirements.
A rare scenario is when you have something like an Active Directory server already provisioned on a network segment that has IP address space that overlaps internal ranges used internally within the VM. Within the Single VM, the internal Kubernetes cluster has internal network ranges. These internal networks are used by Kubernetes within the VM and are not accessible outside the VM, and they should remain as-is unless your existing internal networks overlap those ranges.
In that rare case of overlap, networking issues can happen as the Edge Gateway modules attempt to reach out to Active Directory.
To prevent such conflicts, the wizard's Advanced section provides these fields for you to enter custom values. The ranges that mustn't conflict are:
- 169.254.0.0/16
- 172.30.0.0./16
- 172.31.0.0/16
- 192.0.2.0/24
If your existing internal networks overlap those ranges, you'll provide custom values for these wizard fields. Ensure these two ranges don't overlap or otherwise collide with each other.
- Service CIDR - For the custom value, a minimum of /27 is required.
- Pod CIDR - For the custom value, a minimum of /21 is required.
Was this page helpful?