From 74c36f48972e82e927a4b23a1464ed16dc8eeea3 Mon Sep 17 00:00:00 2001 From: ziirish Date: Wed, 27 Nov 2024 12:06:24 +0100 Subject: [PATCH 01/10] fix(ins): details about routed IPv6 --- compute/instances/how-to/migrate-routed-ips.mdx | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 443b4f7b3a..e153c01fc0 100644 --- 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. +During deployment, each Instance prior April 2024 used to get 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. -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. +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 (more on that bellow). -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. +Using a routed flexible IP is recommended, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring. * 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 +## IPv6 support + +Routed IPs provide flexible IPv6 support. This means one can now assign an IPv6 that will remain the same whenever the Instance is located. Prior routed IPs, IPv6 were assigned per node location, thus whenever an Instance was relocated, its IPv6 was changed. +However, for the best experience, your Instance must be supported (we won't 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. From e3941ea33e86e47ca303364be50af56c4fc60e50 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Wed, 27 Nov 2024 16:31:02 +0100 Subject: [PATCH 02/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index e153c01fc0..b514d2f61a 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -15,7 +15,7 @@ categories: During deployment, each Instance prior April 2024 used to get 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. -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 (more on that bellow). +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 (see below for details). Using a routed flexible IP is recommended, as it allows precise control over network configurations. It simplifies troubleshooting, ensures compatibility with more applications, and allows for enhanced security monitoring. From b0b6a37083f90b3ceea72bc861d3ad67f8e14e5f Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Wed, 27 Nov 2024 16:31:13 +0100 Subject: [PATCH 03/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index b514d2f61a..83795f2b53 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -13,7 +13,7 @@ categories: - compute --- -During deployment, each Instance prior April 2024 used to get 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. +During deployment, each Instance created before April 2024 used to get 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. 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 (see below for details). From 3113086ddd4be3b86b0997c70ed00159b3e52575 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Wed, 27 Nov 2024 16:31:38 +0100 Subject: [PATCH 04/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Fabien Malfoy --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 83795f2b53..d58abde212 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -81,6 +81,6 @@ After the transition finishes, the notification icon will no longer be visible i ## IPv6 support -Routed IPs provide flexible IPv6 support. This means one can now assign an IPv6 that will remain the same whenever the Instance is located. Prior routed IPs, IPv6 were assigned per node location, thus whenever an Instance was relocated, its IPv6 was changed. +Routed IPs provide flexible IPv6 support. This means one 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. However, for the best experience, your Instance must be supported (we won't 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. From 62f65a1ff35822e5bf3ce6f733d77144f33e1345 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:12:29 +0100 Subject: [PATCH 05/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index d58abde212..83d9439f93 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -17,7 +17,7 @@ During deployment, each Instance created before April 2024 used to get a NAT IP 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 (see below for details). -Using a routed flexible IP is recommended, 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. * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature. From 416fede9a6c92814b4981ecd8203512003b41e51 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:12:44 +0100 Subject: [PATCH 06/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 83d9439f93..53d3d9b80f 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -81,6 +81,6 @@ After the transition finishes, the notification icon will no longer be visible i ## IPv6 support -Routed IPs provide flexible IPv6 support. This means one 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. +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. However, for the best experience, your Instance must be supported (we won't 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. From d6e7f9ef8001eaf3976dda507c1192ebf46dd884 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:12:54 +0100 Subject: [PATCH 07/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 53d3d9b80f..9e681ca897 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -82,5 +82,5 @@ After the transition finishes, the notification icon will no longer be visible i ## 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. -However, for the best experience, your Instance must be supported (we won't provide support for EOL Operating Systems). +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. From 8b44a0b712faf24fe578baece49287465c13fd2f Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:13:05 +0100 Subject: [PATCH 08/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 9e681ca897..ad38f8613c 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -15,7 +15,7 @@ categories: During deployment, each Instance created before April 2024 used to get 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. -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 (see below for details). +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. 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. From 8207b09333e8d89eb4336e3ced812a29ed111f34 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:13:25 +0100 Subject: [PATCH 09/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index ad38f8613c..9aa9613a8e 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -83,4 +83,4 @@ After the transition finishes, the notification icon will no longer be visible i 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. +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. From 10377c0d823016abfd4b7f5058a5845585433960 Mon Sep 17 00:00:00 2001 From: "Benjamin \"Ziirish\" SANS" Date: Thu, 28 Nov 2024 16:14:56 +0100 Subject: [PATCH 10/10] Update compute/instances/how-to/migrate-routed-ips.mdx Co-authored-by: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> --- compute/instances/how-to/migrate-routed-ips.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 9aa9613a8e..84d61f5eee 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -13,7 +13,7 @@ categories: - compute --- -During deployment, each Instance created before April 2024 used to get 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. 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.