From d3ba9a2f3d05a356359f259f13c75a3bd61f9fdc Mon Sep 17 00:00:00 2001 From: Rowena Date: Thu, 31 Jul 2025 14:21:02 +0200 Subject: [PATCH 1/3] fix(vpc): serverless routing info --- pages/vpc/faq.mdx | 6 +++++- pages/vpc/troubleshooting/vpc-limitations.mdx | 5 +++-- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/pages/vpc/faq.mdx b/pages/vpc/faq.mdx index 9d4e60146f..119f4ef9c8 100644 --- a/pages/vpc/faq.mdx +++ b/pages/vpc/faq.mdx @@ -44,7 +44,11 @@ NACLs are currently in Public Beta, and configurable only via the [VPC API](http ### Why can I not route traffic to my Managed Database on another Private Network? -Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. +Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. + +## Are Serverless Functions and Containers compatible with VPC routing? + +No, Serverless Functions and Containers are not currently compatible with VPC routing. Functions and Containers attached to a Private Network support egress traffic only, towards other resources on the same Private Network. ### How are NACLs different from security groups? diff --git a/pages/vpc/troubleshooting/vpc-limitations.mdx b/pages/vpc/troubleshooting/vpc-limitations.mdx index e177069c44..d85f8d0e38 100644 --- a/pages/vpc/troubleshooting/vpc-limitations.mdx +++ b/pages/vpc/troubleshooting/vpc-limitations.mdx @@ -15,12 +15,13 @@ This page sets out some current limitations of Scaleway's VPC. - Instances - Elastic Metal servers - Apple silicon (Mac mini) - - Load Balancers + - Load Balancers. - Public Gateways - Managed Databases for PostgreSQL and MySQL - Managed Databases for Redis™ (only during the process of creating the database) - Kubernetes Kapsule (only during the process of creating the Kapsule cluster) - - Serverless Functions and Containers (egress traffic only, with VPC-supporting namespaces) + - Serverless Functions and Containers (egress traffic only, with VPC-supporting namespaces. Not compatible with VPC routing.) - Private Networks are not supported on some legacy Instance offers which have reached EOL, e.g. `VC1`, `START1` and `X64-*GB`. Note that all Instance offers in the [current product catalogue](https://www.scaleway.com/en/pricing/?tags=compute) are supported. - Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. + From c97906cb52decb16dcee47e9875d6bb52fa30f6d Mon Sep 17 00:00:00 2001 From: Rowena Date: Thu, 31 Jul 2025 14:23:59 +0200 Subject: [PATCH 2/3] fix(vpc): another precision --- pages/vpc/reference-content/understanding-routing.mdx | 1 + 1 file changed, 1 insertion(+) diff --git a/pages/vpc/reference-content/understanding-routing.mdx b/pages/vpc/reference-content/understanding-routing.mdx index e4991e7423..27a40f1d60 100644 --- a/pages/vpc/reference-content/understanding-routing.mdx +++ b/pages/vpc/reference-content/understanding-routing.mdx @@ -157,4 +157,5 @@ Alternatively, and aligned with best practice, when the default NACL rule **Deni ## Limitations - Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with VPC routing. Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. +- Serverless Functions and Containers do not support VPC routing. - VPC routing does not currently support virtual IPs. From 0cb359630e66587f3c108c119683757226de480e Mon Sep 17 00:00:00 2001 From: Rowena Jones <36301604+RoRoJ@users.noreply.github.com> Date: Fri, 1 Aug 2025 16:08:29 +0200 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: Thomas TACQUET --- pages/vpc/faq.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/vpc/faq.mdx b/pages/vpc/faq.mdx index 119f4ef9c8..d93911ea8f 100644 --- a/pages/vpc/faq.mdx +++ b/pages/vpc/faq.mdx @@ -46,7 +46,7 @@ NACLs are currently in Public Beta, and configurable only via the [VPC API](http Only Managed PostgreSQL and MySQL Database Instances created after July 28th 2025 are compatible with [VPC routing](/vpc/concepts/#routing). Maintenance scheduled for later in August 2025 will make all pre-existing Managed PostgreSQL and MySQL Database Instances compatible as well. -## Are Serverless Functions and Containers compatible with VPC routing? +### Are Serverless Functions and Containers compatible with VPC routing? No, Serverless Functions and Containers are not currently compatible with VPC routing. Functions and Containers attached to a Private Network support egress traffic only, towards other resources on the same Private Network.