docs(srv): add srv x vpc ref content (#5348)

* docs(srv): add srv x vpc ref content

* docs(srv): update serverless x VPC doc

* Update pages/serverless-containers/reference-content/containers-private-networks.mdx

Co-authored-by: Thomas TACQUET <[email protected]>

* docs(srv): update serverless x VPC doc

* docs(srv): add faas

* docs(srv): add faas

* Apply suggestions from code review

Co-authored-by: Néda <[email protected]>

---------

Co-authored-by: Thomas TACQUET <[email protected]>
Co-authored-by: Néda <[email protected]>

Author: 3 people

menu/navigation.json

@@ -4509,6 +4509,10 @@
                     "label": "Serverless overview",
                     "slug": "serverless-overview"
                   },
+                  {
+                    "label": "Containers and Private Networks integration",
+                    "slug": "containers-private-networks"
+                  },
                   {
                     "label": "Containers limitations",
                     "slug": "containers-limitations"
@@ -4673,6 +4677,10 @@
                     "label": "Functions runtimes",
                     "slug": "functions-runtimes"
                   },
+                  {
+                    "label": "Functions and Private Networks integration",
+                    "slug": "functions-private-networks"
+                  },
                   {
                     "label": "Functions limitations",
                     "slug": "functions-limitations"

pages/organizations-and-projects/additional-content/organization-quotas.mdx

@@ -333,6 +333,12 @@ After you order a server from the list of Elastic Metal servers compatible with
 The maximum RAM quota is obtained by multiplying the maximum scale factor of your container by the selected RAM quantity.
 For example, if you choose to create a container with 512 MB of memory and a maximum scale of 20, you will have 10 GB RAM.
 
+#### Private Networks (VPC) quotas
+
+|                                   | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card)                    | Payment method and [identity validated](/account/how-to/verify-identity/)            |
+|-----------------------------------|:----------------------------------------------------------------------------------------------------------: |:------------------------------------------------------------------------------------:|
+| Maximum attached Private Networks | 5                                                                                                           | 10                                                                                   |
+
 ## Serverless Functions
 
 <ComputeServerlessFunctions />
@@ -354,6 +360,12 @@ For example, if you choose to create a container with 512 MB of memory and a max
 The maximum RAM quota is obtained by multiplying the maximum scale factor of your container by the selected RAM quantity.
 For example, if you choose to create a container with 512 MB of memory and a max scale of 20, you will have 10 GB RAM.
 
+#### Private Networks (VPC) quotas
+
+|                                   | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card)                    | Payment method and [identity validated](/account/how-to/verify-identity/)            |
+|-----------------------------------|:----------------------------------------------------------------------------------------------------------: |:------------------------------------------------------------------------------------:|
+| Maximum attached Private Networks | 5                                                                                                           | 10                                                                                   |
+
 ## Serverless Jobs
 
 <ComputeServerlessJobs />

pages/serverless-containers/how-to/use-private-networks.mdx

@@ -91,4 +91,4 @@ This must be carried out from the VPC section of the console. Follow the procedu
 
 ## Private Networks and containers limitations
 
-For more information on limitations when using Private Networks with Serverless Containers, refer to the [dedicated documentation](/serverless-containers/reference-content/containers-limitations/#private-networks-and-virtual-private-cloud-vpc).
+For more information on limitations when using Private Networks with Serverless Containers, refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks).

pages/serverless-containers/reference-content/containers-limitations.mdx

@@ -84,21 +84,7 @@ Do not have your containers listen on these ports, as they are used by our servi
 
 ## Private Networks and Virtual Private Cloud (VPC)
 
-### Compatibility
-
-Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information.
-
-### Usage
-
-- Containers in the same namespace can be attached to different Private Networks.
-
-- Attaching Serverless Containers to Private Networks does not entail additional cost.
-
-### Limitations
-
-- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-containers/how-to/create-manage-delete-containers-namespace/#creating-a-serverless-containers-namespace), and cannot be updated afterward.
-
-- Only one Private Network can be attached to a container.
+Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-private-networks/) on VPC and Serverless Containers integration for more information.
 
 ## Default values for CPU and memory limits
 

pages/serverless-containers/reference-content/containers-private-networks.mdx

@@ -0,0 +1,34 @@
+---
+title: Serverless Containers and Private Networks integration
+description: This page contains details on how Serverless Containers interacts with Virtual Private Cloud and Private Networks
+dates:
+  posted: 2025-07-29
+  validation: 2025-07-29
+---
+
+## Compatibility
+
+Scaleway Serverless Containers support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-containers/how-to/use-private-networks/) for more information.
+
+## Features
+
+- Containers in the same namespace can be attached to different Private Networks.
+- Both [sandbox](/serverless-containers/concepts/#sandbox) environments (`V1` and `V2`) are compatible with Private Networks.
+- Attaching Serverless Containers to Private Networks **does not incur additional cost**.
+- **Egress** (outbound private traffic from a container to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be routed through the public endpoint of the container.
+- All DNS resolution is done through the Private Network (using the VPC DNS server `169.254.169.254`), which allows to resolve `*.internal` records.
+
+## Quotas
+
+Refer to the [dedicated documentation](/organizations-and-projects/additional-content/organization-quotas/) for more information on Private Networks quotas for Serverless Containers.
+
+## Limitations
+
+- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-containers/how-to/create-manage-delete-containers-namespace/#creating-a-serverless-containers-namespace), and cannot be updated afterward.
+- Only one Private Network can be attached to a Serverless Container.
+- **VPC routing** (custom routes and cross-PN automatic routing) is not supported yet.
+- **Ingress** (inbound private traffic from resources to a container within the same Private Network) is not supported yet.
+- Each [container instance](/serverless-containers/concepts/#instance) has a unique IP automatically assigned by Scaleway in the Private Network. This implies the following:
+    - Users **cannot preemptively book an IP** with [IPAM](/ipam/), and reference it in the attachment.
+    - A single Serverless Container can have a **large number of IPs** being used within the Private Network, depending on the number of concurrent instances.
+    - **Cold-starts are slightly longer** due to the additional steps required to attach the node to the Private Network and book an IP.

pages/serverless-functions/how-to/use-private-networks.mdx

@@ -91,4 +91,4 @@ This must be carried out from the VPC section of the console. Follow the procedu
 
 ## Private Networks and functions limitations
 
-For more information on limitations when using Private Networks with Serverless Functions, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-limitations/#private-networks-and-virtual-private-cloud-vpc).
+For more information on limitations when using Private Networks with Serverless Functions, refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/).

pages/serverless-functions/reference-content/functions-limitations.mdx

@@ -66,21 +66,7 @@ Due to potential abuse (spam), no outbound traffic is allowed through following
 
 ## Private Networks and Virtual Private Cloud (VPC)
 
-### Usage
-
-- Functions in the same namespace can be attached to different Private Networks.
-
-- Attaching Serverless Functions to Private Networks does not entail additional cost.
-
-### Compatibility
-
-Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information.
-
-### Limitations
-
-- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-functions-namespace/#creating-a-serverless-functions-namespace), and cannot be updated afterward.
-
-- Only one Private Network can be attached to a function.
+Refer to the [dedicated documentation](/serverless-functions/reference-content/functions-private-networks/) on VPC and Serverless Functions integration for more information.
 
 ## Versioning and rollback
 

pages/serverless-functions/reference-content/functions-private-networks.mdx

@@ -0,0 +1,34 @@
+---
+title: Serverless Functions and Private Networks integration
+description: This page contains details on how Serverless Functions interacts with Virtual Private Cloud and Private Networks
+dates:
+  - posted: 2025-08-04
+  - validation: 2025-08-04
+---
+
+## Compatibility
+
+Scaleway Serverless Functions support [Virtual Private Cloud (VPC)](/vpc/) and can be attached to a Private Network, which allows you to securely connect your resources in an isolated environment. Refer to the [dedicated documentation](/serverless-functions/how-to/use-private-networks/) for more information.
+
+## Features
+
+- Functions in the same namespace can be attached to different Private Networks.
+- Both [sandbox](/serverless-functions/concepts/#sandbox) environments (`V1` and `V2`) are compatible with Private Networks.
+- Attaching Serverless Functions to Private Networks **does not incur additional cost**.
+- **Egress** (outbound private traffic from a function to resources within the same Private Network) will be routed through the private interface, but external traffic (from the Internet) will be routed through the public endpoint of the function.
+- All DNS resolution is done through the Private Network (using the VPC DNS server `169.254.169.254`), which allows to resolve `*.internal` records.
+
+## Quotas
+
+Refer to the [dedicated documentation](/organizations-and-projects/additional-content/organization-quotas/) for more information on Private Networks quotas for Serverless Functions.
+
+## Limitations
+
+- VPC works with Namespaces that have **VPC support enabled**. VPC support can only be enabled at [namespace creation](/serverless-functions/how-to/create-manage-delete-functions-namespace/#creating-a-serverless-functions-namespace), and cannot be updated afterward.
+- Only one Private Network can be attached to a Serverless Container.
+- **VPC routing** (custom routes and cross-PN automatic routing) is not supported yet.
+- **Ingress** (inbound private traffic from resources to a function within the same Private Network) is not supported yet.
+- Each [function instance](/serverless-functions/concepts/#instance) has a unique IP automatically assigned by Scaleway in the Private Network. This implies the following:
+    - Users **cannot preemptively book an IP** with [IPAM](/ipam/), and reference it in the attachment.
+    - A single Serverless Container can have a **large number of IPs** being used within the Private Network, depending on the number of concurrent instances.
+    - **Cold-starts are slightly longer** due to the additional steps required to attach the node to the Private Network and book an IP.