From ba9ab6500e76a4d11a5676e671d821449e2c2ad0 Mon Sep 17 00:00:00 2001 From: thomas-tacquet Date: Tue, 29 Oct 2024 09:59:49 +0100 Subject: [PATCH 1/2] fix(serverless): faq title level --- faq/serverless-containers.mdx | 4 ++-- faq/serverless-jobs.mdx | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx index 3d27192425..9345cfcaad 100644 --- a/faq/serverless-containers.mdx +++ b/faq/serverless-containers.mdx @@ -97,11 +97,11 @@ Ensure that your code avoids heavy computations or long-running initialization a Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless/containers/reference-content/containers-limitations/) for more information. -# Where should I host my container images for deployment ? +## Where should I host my container images for deployment ? -# How can I copy an image from an external registry to Scaleway Container Registry? +## How can I copy an image from an external registry to Scaleway Container Registry? You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below: diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx index fb7baf3451..7b9e8b216b 100644 --- a/faq/serverless-jobs.mdx +++ b/faq/serverless-jobs.mdx @@ -94,11 +94,11 @@ Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information. -# Where should I host my jobs images for deployment ? +## Where should I host my jobs images for deployment ? -# How can I copy an image from an external registry to Scaleway Container Registry? +## How can I copy an image from an external registry to Scaleway Container Registry? You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below: @@ -119,4 +119,4 @@ skopeo copy --override-os linux docker://docker.io/alpine:latest docker://rg.fr- 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. \ No newline at end of file +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. From 6fb36f1d18c7d0636e237a283dd6f4b5371d939c Mon Sep 17 00:00:00 2001 From: thomas-tacquet Date: Tue, 29 Oct 2024 10:06:51 +0100 Subject: [PATCH 2/2] one more --- faq/serverless-containers.mdx | 2 +- faq/serverless-functions.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx index 9345cfcaad..755f98b150 100644 --- a/faq/serverless-containers.mdx +++ b/faq/serverless-containers.mdx @@ -153,7 +153,7 @@ Scaleway Serverless Containers do not currently support attaching block storage. stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. -# Why does my container have an instance running after deployment, even with min-scale 0? +## Why does my container have an instance running after deployment, even with min-scale 0? Currently, a new container instance will always start after each deployment, even if there is no traffic and the minimum scale is set to 0. This behavior is not configurable at this time. diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx index b4702d3727..708e500fe9 100644 --- a/faq/serverless-functions.mdx +++ b/faq/serverless-functions.mdx @@ -180,7 +180,7 @@ Scaleway Serverless Functions do not currently support attaching block storage. stateless, meaning they do not retain data between invocations. For persistent storage, we recommend using external solutions like Scaleway Object Storage. -# Why does my function have an instance running after deployment, even with min-scale 0? +## Why does my function have an instance running after deployment, even with min-scale 0? Currently, a new function instance will always start after each deployment, even if there is no traffic and the minimum scale is set to 0. This behavior is not configurable at this time.