Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate Scaleway instances to Routed IP #271

Closed
benoit74 opened this issue Sep 27, 2024 · 1 comment
Closed

Migrate Scaleway instances to Routed IP #271

benoit74 opened this issue Sep 27, 2024 · 1 comment
Assignees
Labels
maint Maintenance tasks time-sensitive Must be adressed rapidly

Comments

@benoit74
Copy link
Collaborator

Scaleway said:

Hi,
In our last communication, we shared with you the upcoming evolution of our network stack, including dates regarding the move to Routed IPs.
Since March 2024, Instance users have been invited to manually move their instances to the new stack. Today, we announce the next step in this evolution, with the automatic move from NAT to Routed IPs. This means all Instances will be using a Routed IP, following that process.
As previously announced, we are also deprecating the NAT IP addresses on Instances to further improve the reliability of our services.
This automatic move will occur on different batches by AZ between October 7th and November 30th 2024. This also means that from October 7, 2024, creating Instances with NAT IPs will no longer be possible.
How will you be impacted?
During this intervention, each Instance will be stopped, allowing the IP to be moved from NAT to Routed. It will automatically be restarted, with the same IP address. In most cases, the interruption will last approximately 5 minutes. If your Instance is already stopped, it will not be restarted.
We strongly encourage you to refer to this guide available in our documentation website, should you want to manually move your Instance before the scheduled intervention. If you have any scripts calling the API directly to create Instances with NAT IPs, please update it to use Routed IPs. If you are using our CLI or Terraform adapter, please update to the latest version to support these changes.
Instances used by Kapsule are not concerned by this automatic move. They will roll out their own migration strategies as described here.
When is it planned?
The first batch will start on October 7th, 2024. As usual, you will be notified by a ticket on the exact date that your VM will be moved.
We appreciate your understanding and cooperation during this transition period.

Doc: https://www.scaleway.com/en/docs/compute/instances/how-to/migrate-routed-ips/

I think we should do the migration to Routed IP manually to ensure we are available to monitor / restore systems should the transition go bad. So we need to do it before 7th of October.

@benoit74 benoit74 added time-sensitive Must be adressed rapidly maint Maintenance tasks labels Sep 27, 2024
@benoit74
Copy link
Collaborator Author

benoit74 commented Oct 1, 2024

We have only one Cloud Instance ATM: bastion.

I migrated it to Routed IP few minutes ago, instance is back up, all containers seems to be back online. Monitoring the situation.

@benoit74 benoit74 closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maint Maintenance tasks time-sensitive Must be adressed rapidly
Projects
None yet
Development

No branches or pull requests

2 participants