fix(ins): details about routed IPv6 (#4044)

* fix(ins): details about routed IPv6 * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> * Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <[email protected]> --------- Co-authored-by: Fabien Malfoy <[email protected]> Co-authored-by: Rowena Jones <[email protected]>
scaleway · Nov 28, 2024 · 300d765 · 300d765
1 parent cad29c5
commit 300d765
Showing 1 changed file with 8 additions and 3 deletions.
diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx
@@ -13,11 +13,11 @@ categories:
   - compute
 ---
 
-During deployment, each Instance gets a NAT IP from its hosting node, besides its public IP, which is routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. However, if the underlying hypervisor changes, the NAT IP changes. This can happen when you restart your Instance. The NAT IP lets Instances communicate via an underlying internal network, without public IPs.
+Prior to April 2024, all Instances got a NAT IP from their hosting node, which was routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-(cgnat)) solution. This was in addition to the public (flexible) IP. The NAT IP let Instances communicate via an underlying internal network, without public IPs. However, if the underlying hypervisor changed, the NAT IP changed also. This could happen when you restarted your Instance. 
 
-Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported.
+Since October 2024 it is no no longer possible to create Instances with NAT IPs. Instead, Instances' public IPs are **routed** IPs. Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported.
 
-Using a routed flexible IP is recommended for all compatible Instance types, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring.
+In addition to the benefits explained above, routed IPs allow precise control over network configurations, simplify troubleshooting, ensure compatibility with more applications, and allow for enhanced security monitoring. We recommend that users with Instances still using NAT IPs  move them to routed IPs by following the instructions below. 
 
 <Message type="important">
   * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature.
@@ -79,3 +79,8 @@ After the transition finishes, the notification icon will no longer be visible i
 </Message>
 
 
+## IPv6 support
+
+Routed IPs provide flexible IPv6 support. This means you can now assign an IPv6 address that will remain the same wherever the Instance is located. Before the advent of routed IPs, IPv6 addresses were assigned per node location, thus whenever an Instance was relocated, its IPv6 address was changed.
+Note that for the best experience with IPv6, your Instance must be supported (we do not provide support for EOL Operating Systems).
+For IPv6 only, you need `cloud-init` version [23.2](https://github.com/canonical/cloud-init/releases/tag/23.2) or later and `scaleway-ecosystem` version 0.6 or later.