Migrate your IPv4-only VMs

IPv4-only VMs are deprecated - you can no longer create new IPv4-only VMs. Existing IPv4-only VMs continue to work, but you should migrate them to dual-stack or ipv6-only.

Important: This page covers the migration of existing IPv4-only VMs only. For a complete list of new features and other changes in v1beta2, see What's new in the v1beta2 release.

What changed

The v1beta2 release adds a stackType field to VMs. In releases earlier than v1beta2, all VMs were effectively IPv4-only — there was no stack type to configure.

New VMs must use dual-stack or ipv6-only. The ipv4-only stack type is deprecated and can't be set on new VMs.

What you need to do

If you have existing IPv4-only VMs, migrate them to dual-stack (if you need IPv4 networking) or ipv6-only.

To migrate a VM, use the evroc CLI:

  1. Stop the VM:

    evroc compute virtualmachine update myvm --running=false

  2. Update the VM's stack type to dual-stack (if IPv4 networking is desired) or ipv6-only:

    evroc compute virtualmachine update myvm --stack-type=dual-stack

  3. Start the VM again:

    evroc compute virtualmachine update myvm --running=true

You can check a VM's stack type and addresses using:

evroc compute virtualmachine get myvm

Look for the stackType, privateIPv4Address, and ipv6Address fields in the output.

Configuring security groups to use IPv6

To use IPv6 on pre-existing VMs, you must configure security groups which allow IPv6 connectivity. This requirement applies to any security group rule which uses a remote IP or CIDR for the remote.

For example, to create a security group which allows all IPv6 egress traffic in the default VPC, use:

evroc networking securitygroup create allow-ipv6-egress

evroc networking securitygroup addrule allow-ipv6-egress \
  --name=allow-egress-ipv6 \
  --direction=Egress \
  --remote-ip-or-cidr=::/0 \
  --protocol=All

You must then configure this security group on the VMs which require IPv6 egress connectivity.