Important: Migrate your VMs by 31 July 2026

All existing IPv4-only virtual machines (VMs) must be migrated to dual-stack or ipv6-only by 31 July 2026. After this date, evroc automatically upgrades any remaining IPv4-only VMs to dual-stack.

Important: This page covers the migration requirement 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.

What you need to do

VMs created before v1beta2 remain as-is and have a stack type of ipv4-only. You have until 31 July 2026 to convert them yourself. After this date, evroc automatically upgrades any remaining IPv4-only VMs to dual-stack. The VM receives a globally routable IPv6 Global Unicast Address (GUA) in addition to its existing IPv4 address.

To migrate a VM:

  1. Stop the VM.
  2. Update the VM to set its stack type to dual-stack (if IPv4 networking is desired) or ipv6-only.
  3. Start the VM again.

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.