Skip to content

Commit 29619c5

Browse files
yfodilremyleone
andauthored
Update docs/guides/migration_guide_vpcgw_v2.md
Co-authored-by: Rémy Léone <[email protected]>
1 parent fe580d7 commit 29619c5

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/guides/migration_guide_vpcgw_v2.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ page_title: "Moving a Public Gateway from Legacy mode to IPAM mode, for v2 compa
44

55
# Moving a Public Gateway from Legacy mode to IPAM mode
66

7-
This guide explains how to move a Public Gateway from [Legacy mode](https://www.scaleway.com/en/docs/public-gateways/concepts/#ipam) to IPAM mode. Only gateways in IPAM mode will be compatible with the new v2 of the Public Gateways API. v1 of the API is deprecated, and will be removed later this year.
7+
This guide explains how to move a Public Gateway from [Legacy mode](https://www.scaleway.com/en/docs/public-gateways/concepts/#ipam) to IPAM mode. Only gateways in IPAM mode will be compatible with the new v2 of the Public Gateways API. v1 of the API is deprecated, and will be removed before the end of 2025.
88
In the legacy setup, DHCP and DHCP reservations are managed with dedicated resources and referenced in the gateway network.
99
In IPAM mode, these functionalities are managed by Scaleway IPAM.
1010
In 2023, DHCP functionality was moved from Public Gateways to Private Networks, DHCP resources are now no longer needed.

0 commit comments

Comments
 (0)