diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx index 848e9e81f9..56f020b400 100644 --- a/faq/serverless-containers.mdx +++ b/faq/serverless-containers.mdx @@ -119,3 +119,10 @@ Containers use http1 by default, yet the gRPC protocol requires http2. You can u A Serverless Container is set to `ready` once the specified port is correctly bound to the container, and will start receiving traffic. If your application needs to perform some tasks before receiving traffic (e.g. connect to a database), it's important to run them before binding to the port (starting the webserver). For now, the `HEALTHCHECK` Docker directive has no impact on container readiness. In the future, the healthcheck will be customizable for your applications. + +## How can I configure access to a Private Network? + +Scaleway Serverless Containers does not currently support Scaleway VPC or Private Networks, though this feature is under development. + +To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses. + diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx index 2806fed34b..64127885be 100644 --- a/faq/serverless-functions.mdx +++ b/faq/serverless-functions.mdx @@ -167,3 +167,9 @@ Check out our [serverless-examples repository](https://github.com/scaleway/serve There are no constraints when changing a function runtime, you simply need to choose the runtime version you want. Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information. + +## How do I configure access to a Private Network? + +Scaleway Serverless Functions does not currently support Scaleway VPC or Private Networks, though this feature is under development. + +To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Note that Serverless resources do not have dedicated or predictable IP addresses. diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx index 71d06e0887..4e2ea81950 100644 --- a/faq/serverless-jobs.mdx +++ b/faq/serverless-jobs.mdx @@ -93,3 +93,10 @@ Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be ## Do Serverless Jobs offer parallelization? Not yet. Scaleway Serverless Jobs will soon offer parallelization via a `parallelism` parameter for each job. This will automatically launch a given number of replicas of the Job container in parallel. + +## How can I configure access to a Private Network? + +Scaleway Serverless Jobs does not currently support Scaleway VPC or Private Networks, though this feature is under development. + +To add network restrictions on your resource, consult the [list of prefixes used at Scaleway](https://www.scaleway.com/en/peering/). Serverless resources do not have dedicated or predictable IP addresses. +