diff --git a/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx b/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx index b05596906a..8ce9b39401 100644 --- a/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx +++ b/pages/serverless-containers/how-to/create-manage-delete-containers-namespace.mdx @@ -24,7 +24,6 @@ This page shows you how to create and manage a Serverless Containers namespace. - Enter a **name** or use the automatically generated one. The name must only contain alphanumeric characters and dashes. - Enter an optional **description** and **tags**. - Choose a **region**, which is the geographical location in which your namespace will be deployed. - - Tick the **Enable VPC support** if you want to create containers within this namespace that you can attach to a [Private Network](/serverless-functions/concepts/#private-networks). - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+ Add new variable** and enter the key / value pair. - Set secret environment variables (optional). **Secrets** are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. - Verify the **estimated cost**. diff --git a/pages/serverless-containers/how-to/use-private-networks.mdx b/pages/serverless-containers/how-to/use-private-networks.mdx index afac06de23..f2f43a222b 100644 --- a/pages/serverless-containers/how-to/use-private-networks.mdx +++ b/pages/serverless-containers/how-to/use-private-networks.mdx @@ -13,10 +13,6 @@ import Requirements from '@macros/iam/requirements.mdx' For full information about Scaleway Private Networks and VPC, see our [dedicated documentation](/vpc/) and [best practices guide](/vpc/reference-content/getting-most-private-networks/). - -The Private Networks feature can only be enabled on newly created namespaces. Existing namespaces that do not have the feature enabled cannot be integrated in a Private Network. - - - A Scaleway account logged into the [console](https://console.scaleway.com) @@ -26,24 +22,7 @@ The Private Networks feature can only be enabled on newly created namespaces. Ex ## How to create a Private Network -This action must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/create-private-network/). - -## How to create a Private Networks-enabled namespace - -Before attaching a Private Network to a Serverless Container, you must create it within a namespace with the Private Networks feature enabled. - -1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. - -2. Click **+ Create namespace**. If you have no existing Serverless Containers resources in your current Project, click **Create a container**. The containers namespace creation wizard displays. - -3. Complete the following steps in the wizard: - - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - - Enter an optional **description** and **tags**. - - Choose a **region**, which is the geographical location in which your namespace will be deployed. - - Tick the **Enable VPC support** box. This parameter cannot be edited once the namespace is created. - - Click **+ Add advanced options** to define any **environment variables** you want to inject into your container. For each environment variable, click **+ Add variable** and enter the key/value pair. - - Set optional secret environment variables. **Secrets** are environment variables which are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. -4. Click **Create namespace only** to finish, or click **Create namespace and add a container** if you want to [create a container](/serverless-containers/how-to/build-push-container-image/) next. +This action must be carried out from the Private Networks section of the console. Follow the procedure detailed in our [dedicated Private Networks documentation](/vpc/how-to/create-private-network/). ## How to attach a Serverless Container to a Private Network @@ -53,17 +32,17 @@ Before attaching a Private Network to a Serverless Container, you must create it 2. Click the relevant containers namespace. 3. Click the name of the container you want to manage. 4. Open the **Settings** tab, then scroll to the **Advanced options** section. - 5. In the **VPC** tab, select a Private Network from the dropdown menu. + 5. In the **Private Networks** tab, select a Private Network from the dropdown menu. 6. Click **Save container settings**. - + Your container is redeployed, and is now attached to the selected Private Network. 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. - 2. Click the **Private Networks-enabled** containers namespace in which you want to create your container. + 2. Click the **containers namespace** in which you want to create your container. 3. Click **+ Create container**. The container creation wizard displays. 4. Scroll to the **Advanced options** section. - 5. In the **VPC** tab, select a Private Network from the dropdown menu. + 5. In the **Private Networks** tab, select a Private Network from the dropdown menu. 6. Configure the other parameters of your container, then click **Create container**. Refer to the [How to create a container](/serverless-containers/how-to/build-push-container-image/) for more information. Your new container is deployed, and is attached to the selected Private Network. @@ -76,7 +55,7 @@ Before attaching a Private Network to a Serverless Container, you must create it 2. Click the relevant containers namespace. 3. Click the name of the container you want to manage. 4. Open the **Settings** tab, then scroll to the **Advanced options** section. -5. In the **VPC** tab, click the icon next to the Private Network attached to your container. +5. In the **Private Networks** tab, click the icon next to the Private Network attached to your container. 6. Click **Save container settings**. Your container is redeployed and is now detached from the Private Network. @@ -87,7 +66,7 @@ Your container is redeployed and is now detached from the Private Network. Before deleting a Private Network, you must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources attached to it. -This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/). +This must be carried out from the Private Networks section of the console. Follow the procedure detailed in our [dedicated Private Networks documentation](/vpc/how-to/delete-private-network/). ## Private Networks and containers limitations diff --git a/pages/serverless-containers/reference-content/containers-private-networks.mdx b/pages/serverless-containers/reference-content/containers-private-networks.mdx index 8259580c08..390066a1a8 100644 --- a/pages/serverless-containers/reference-content/containers-private-networks.mdx +++ b/pages/serverless-containers/reference-content/containers-private-networks.mdx @@ -24,7 +24,6 @@ Refer to the [dedicated documentation](/organizations-and-projects/additional-co ## 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. diff --git a/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx b/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx index bd13d6ee92..e24aee666e 100644 --- a/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx +++ b/pages/serverless-functions/how-to/create-manage-delete-functions-namespace.mdx @@ -28,7 +28,6 @@ This page shows you how to create, manage, and delete a Functions namespace usin - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Enter an optional **description** and **tags**. - Choose a **region**, which is the geographical location in which your namespace will be deployed. - - Tick the **Enable VPC support** if you want to create functions within this namespace that you can attach to a [Private Network](/serverless-functions/concepts/#private-networks). - Click **+ Add advanced options** to define any **environment variables** you want to inject into your function. For each environment variable, click **+ Add variable** and enter the key/value pair. - Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. 4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless-functions/how-to/create-a-function/) next. diff --git a/pages/serverless-functions/how-to/use-private-networks.mdx b/pages/serverless-functions/how-to/use-private-networks.mdx index 6988d5ad99..0cb4e9ad47 100644 --- a/pages/serverless-functions/how-to/use-private-networks.mdx +++ b/pages/serverless-functions/how-to/use-private-networks.mdx @@ -8,42 +8,19 @@ dates: --- import Requirements from '@macros/iam/requirements.mdx' - [Private Networks](/serverless-functions/concepts/#private-networks) allow your Serverless Functions to communicate in an isolated and secure network without needing to be connected to the public internet. Each function can be connected to one or several Private Networks, letting you build your own network topologies. For full information about Scaleway Private Networks and VPC, see our [dedicated documentation](/vpc/) and [best practice guide](/vpc/reference-content/getting-most-private-networks/). - -The Private Networks feature can only be enabled on newly created namespaces. Existing namespaces that do not have the feature enabled cannot be integrated in a Private Network. - - - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Created a Private Network](/vpc/how-to/create-private-network/) - ## How to create a Private Network -This action must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/create-private-network/). - -## How to create a Private Networks-enabled namespace - -Before attaching a Private Network to a Serverless Function, you must create it within a namespace with the Private Networks feature enabled. - -1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. - -2. Click **+ Create namespace**. If you have no existing Serverless Functions resources in your current Project, click **Create a function**. The functions namespace creation wizard displays. - -3. Complete the following steps in the wizard: - - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - - Enter an optional **description** and **tags**. - - Choose a **region**, which is the geographical location in which your namespace will be deployed. - - Tick the **Enable VPC support** box. This parameter cannot be edited once the namespace is created. - - Click **+ Add advanced options** to define any **environment variables** you want to inject into your function. For each environment variable, click **+ Add variable** and enter the key/value pair. - - Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. -4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless-functions/how-to/create-a-function/) next. +This action must be carried out from the Private Networks section of the console. Follow the procedure detailed in our [dedicated Private Networks documentation](/vpc/how-to/create-private-network/). ## How to attach a Serverless Function to a Private Network @@ -53,17 +30,17 @@ Before attaching a Private Network to a Serverless Function, you must create it 2. Click the relevant functions namespace. 3. Click the name of the function you want to manage. 4. Open the **Settings** tab, then scroll to the **Advanced options** section. - 5. In the **VPC** tab, select a Private Network from the dropdown menu. + 5. In the **Private Networks** tab, select a Private Network from the dropdown menu. 6. Click **Save function settings**. - + Your function is redeployed, and is now attached to the selected Private Network. 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. - 2. Click the **Private Networks-enabled** functions namespace in which you want to create your function. + 2. Click the **functions namespace** in which you want to create your function. 3. Click **+ Create function**. The function creation wizard displays. 4. Scroll to the **Advanced options** section. - 5. In the **VPC** tab, select a Private Network from the dropdown menu. + 5. In the **Private Networks** tab, select a Private Network from the dropdown menu. 6. Configure the other parameters of your function, then click **Create function**. Refer to the [How to create a function](/serverless-functions/how-to/create-a-function/) for more information. Your new function is deployed, and is attached to the selected Private Network. @@ -76,7 +53,7 @@ Before attaching a Private Network to a Serverless Function, you must create it 2. Click the relevant functions namespace. 3. Click the name of the function you want to manage. 4. Open the **Settings** tab, then scroll to the **Advanced options** section. -5. In the **VPC** tab, click the icon next to the Private Network attached to your function. +5. In the **Private Networks** tab, click the icon next to the Private Network attached to your function. 6. Click **Save function settings**. Your function is redeployed and is now detached from the Private Network. @@ -87,7 +64,7 @@ Your function is redeployed and is now detached from the Private Network. Before deleting a Private Network, you must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources attached to it. -This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/). +This must be carried out from the Private Networks section of the console. Follow the procedure detailed in our [dedicated Private Networks documentation](/vpc/how-to/delete-private-network/). ## Private Networks and functions limitations diff --git a/pages/serverless-functions/reference-content/functions-private-networks.mdx b/pages/serverless-functions/reference-content/functions-private-networks.mdx index 5a81b550f2..6f055de915 100644 --- a/pages/serverless-functions/reference-content/functions-private-networks.mdx +++ b/pages/serverless-functions/reference-content/functions-private-networks.mdx @@ -24,7 +24,6 @@ Refer to the [dedicated documentation](/organizations-and-projects/additional-co ## 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. diff --git a/pages/vpc/troubleshooting/vpc-limitations.mdx b/pages/vpc/troubleshooting/vpc-limitations.mdx index d85f8d0e38..f799ad7520 100644 --- a/pages/vpc/troubleshooting/vpc-limitations.mdx +++ b/pages/vpc/troubleshooting/vpc-limitations.mdx @@ -20,8 +20,8 @@ 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. Not compatible with VPC routing.) + - Serverless Functions and Containers (egress traffic only. 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. +- 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.