fix(vpc): update doc (#5306)

RoRoJ · web-flow · commit 45682532deb6 · 2025-07-22T09:56:29.000+02:00
diff --git a/pages/vpc/assets/scaleway-vpc-basics.webp b/pages/vpc/assets/scaleway-vpc-basics.webp
diff --git a/pages/vpc/how-to/attach-resources-to-pn.mdx b/pages/vpc/how-to/attach-resources-to-pn.mdx
@@ -32,6 +32,7 @@ The following resource types can be attached to a Private Network:
     - Load Balancers
     - Public Gateways
     - Managed Databases for PostgreSQL and MySQL
+    - Serverless Functions and Containers
 
     <Message type="note">
     Kubernetes Kapsule clusters and Managed Databases for Redis™ are also compatible with Private Networks, but they can only be attached to a Private Network at the time of creating the resource. It is not possible to attach a cluster or Redis™ database to a Private Network after its creation, or change the attached Private Network.
@@ -85,7 +86,7 @@ The following resource types can be attached to a Private Network:
         - Select whether to **auto-allocate an available IP** from the pool of addresses for the Private Network or **specify an IP** that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). 
 
         <Message type="note">
-        Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases and Apple silicon will be coming soon. In the meantime, you must auto-allocate IPs for these products.
+        Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases, Apple silicon and Serverless will be coming soon. In the meantime, you must auto-allocate IPs for these products.
         </Message>
         </TabsTab>
 
@@ -116,8 +117,10 @@ You can also attach a managed resource to a Private Network from the resource's
 - [Managed Database for PostgreSQL and MySQL](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/)
 - [Load Balancer](/load-balancer/how-to/use-with-private-network/)
 - [Public Gateway](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network)
+- [Serverless Functions](/serverless-functions/how-to/use-private-networks/)
+- [Serverless Containers](/serverless-containers/how-to/use-private-networks/)
 
-Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself.
+Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself. Serverless Functions and Containers can only be attached to Private Networks if they have been created in a namespace that supports VPC.
 </Message>
 
 For Elastic Metal servers and Apple silicon Mac minis, manual configuration of the network interface is required. This is not required for Instances or other types of managed resource. See the relevant documentation for [Elastic Metal](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) or [Apple silicon](/apple-silicon/how-to/use-private-networks/) for full instructions.
diff --git a/pages/vpc/quickstart.mdx b/pages/vpc/quickstart.mdx
@@ -131,7 +131,7 @@ You can create multiple Private Networks within each VPC. Resources attached to
         - Select whether to **auto-allocate an available IP** from the pool of addresses for the Private Network or **specify an IP** that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). 
 
         <Message type="note">
-        Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases and Apple silicon will be coming soon. In the meantime, you must auto-allocate IPs for these products.
+        Only Instances, Load Balancers, Public Gateways, and Elastic Metal servers are compatible with reserved IPs. Support for Managed Databases, Apple silicon and Serverless will be coming soon. In the meantime, you must auto-allocate IPs for these products.
         </Message>
         </TabsTab>
 
diff --git a/pages/vpc/reference-content/getting-most-private-networks.mdx b/pages/vpc/reference-content/getting-most-private-networks.mdx
@@ -119,13 +119,13 @@ Different types of Scaleway resources may have different requirements and possib
 | Documentation | [Go](/instances/how-to/use-private-networks/) | [Go](/elastic-metal/how-to/use-private-networks/) | [Go](/apple-silicon/how-to/use-private-networks/) | [Go](/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster) | [Go](/managed-inference/how-to/managed-inference-with-private-network/) |
 
 
-|                              | Managed Database | Managed Database for Redis™ | Public Gateways | Load Balancer |
-|------------------------------|------------------|-----------------------------|-----------------|---------------|
-| Max attached PNs             | 1                | 1                           | 8               | 8             |
-| Mandatory PN                 | No               | No                          | No              | No            |
-| Compatible with private IPv6 | No               | No                          | No              | No            |
-| Compatible with reserved IPs | No               | No                          | Yes             | Yes           |
-| Additional information       | Must have at least one of <br/> private and/or public endpoint | Must have at least one of <br/> private and/or public endpoint | -- | Private LBs must have a PN |
-| Documentation | [Go](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/managed-databases-for-redis/faq/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/load-balancer/how-to/use-with-private-network/)
+|                              | Managed Database | Managed Database for Redis™ | Public Gateways | Load Balancer | Serverless Functions & Containers |
+|------------------------------|------------------|-----------------------------|-----------------|---------------|----------------------|
+| Max attached PNs             | 1                | 1                           | 8               | 8             | 1                    |
+| Mandatory PN                 | No               | No                          | No              | No            | No                   |
+| Compatible with private IPv6 | No               | No                          | No              | No            | No
+| Compatible with reserved IPs | No               | No                          | Yes             | Yes           | No
+| Additional information       | Must have at least one of <br/> private and/or public endpoint | Must have at least one of <br/> private and/or public endpoint | -- | Private LBs must have a PN | Egress traffic only, from VPC-supported namespaces. |
+| Documentation | [Go](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/managed-databases-for-redis/faq/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/load-balancer/how-to/use-with-private-network/) | [Go](/serverless-functions/how-to/use-private-networks/)
 
 
diff --git a/pages/vpc/troubleshooting/vpc-limitations.mdx b/pages/vpc/troubleshooting/vpc-limitations.mdx
@@ -22,5 +22,6 @@ This page sets out some current limitations of Scaleway's VPC.
   - 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)
 - 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.
 - Managed Databases are not currently compatible with VPC routing. The VPC cannot automatically route between Managed Databases on different Private Networks, or (for example) between a Managed Database on one Private Network and an Instance on a different Private Network.
