From 30c37d4b5575265d3288be5b4dccf636b54cadd0 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Mon, 9 Feb 2026 17:54:15 +0100 Subject: [PATCH 1/2] chore(serverless): concepts general update --- pages/serverless-containers/concepts.mdx | 6 ++- .../containers-concurrency.mdx | 44 ++++++++++--------- pages/serverless-functions/concepts.mdx | 4 +- 3 files changed, 31 insertions(+), 23 deletions(-) diff --git a/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index b5829a2af8..d5061b016b 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -107,6 +107,10 @@ Environment variables are key/value pairs injected into your container. They are Some names are reserved. [See details about reserved names](/serverless-containers/reference-content/containers-limitations/#configuration-restrictions). +If a variable is defined in both your `Dockerfile` and Servlerless Containers service, the Serverless Containers configuration takes precedence. + +For sensitive information we encourage to use [Secret environment variables](/serverless-containers/concepts/#secrets). + ## Ephemeral storage In addition to vCPU and RAM, Serverless Containers also provide a storage volume for the duration of the task. This storage space allows you to hold data during the life of the Servlerless Container instance and disappears once the execution is complete. @@ -223,7 +227,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/ ## Secrets -Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Secrets defined at the container level override the ones defined at the namespace level if they have the same name. +Secrets are an extra-secure type of [environment variable](/serverless-containers/concepts/#environment-variables). They are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Secrets defined at the container level override the ones defined at the namespace level if they have the same name. Secrets on Serverless Containers are not linked with Secret Manager product yet. diff --git a/pages/serverless-containers/reference-content/containers-concurrency.mdx b/pages/serverless-containers/reference-content/containers-concurrency.mdx index ab360567f0..388aa20b8f 100644 --- a/pages/serverless-containers/reference-content/containers-concurrency.mdx +++ b/pages/serverless-containers/reference-content/containers-concurrency.mdx @@ -9,32 +9,34 @@ tags: serverless containers concurrency concurrent execution scaling parallelism ## Concurrency overview -Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload. +Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload. + +Unlike Serverless Functions which handles only one request per instance, Serverless Containers is designed to handle multiple requests simultaneously within one container. This is a powerful feature for optimizing performance and reducing costs. A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless-containers/concepts/#vcpu), and consequently a higher cost. ``` - Concurrency = 1 - - ┌─────────────┐ - │ ┌──────┐│ - │ │ │ ││ - └─────┼───► │ ││ Concurrency = 80 - │ │ ││ - │ └──────┘│ ┌─────────────┐ - │ ┌──────┐│ │ │ ┌──────┐│ - │ │ ││ └────┼───► │ ││ -3 requests ──────┼───► │ ││ 3 requests ─────┼───► │ ││ - │ │ ││ ┌────┼───► │ ││ - │ └──────┘│ │ │ └──────┘│ - │ ┌──────┐│ └─────────────┘ - │ │ ││ 1 service + Concurrency = 1 + + ┌─────────────┐ + │ ┌──────┐│ + │ │ │ ││ + └─────┼───► │ ││ Concurrency = 80 + │ │ ││ + │ └──────┘│ ┌─────────────┐ + │ ┌──────┐│ │ │ ┌──────┐│ + │ │ ││ └────┼───► │ ││ +3 requests ──────┼───► │ ││ 3 requests ─────┼───► │ ││ + │ │ ││ ┌────┼───► │ ││ + │ └──────┘│ │ │ └──────┘│ + │ ┌──────┐│ └─────────────┘ + │ │ ││ 1 service ┌─────┼───► │ ││ 1 container instance - │ │ │ ││ - │ └──────┘│ - └─────────────┘ - 1 service - 3 container instances + │ │ │ ││ + │ └──────┘│ + └─────────────┘ + 1 service + 3 container instances ``` ## Concurrency setting diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index fd90ca7f13..9640c58215 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -59,6 +59,8 @@ Environment variables are key/value pairs injected into your function. They are Some names are reserved. [See details on reserved names](/serverless-functions/reference-content/functions-limitations/#configuration-restrictions). +For sensitive information we encourage to use [Secret environment variables](/serverless-functions/concepts/#secrets). + ## GB-s Unit used to measure the resource consumption of a Serverless Function. It reflects the amount of memory consumed over time. @@ -190,7 +192,7 @@ When provisioned with a [minimum scale](#min-scale) of `0`, Serverless Functions ## Secrets -Secrets are an extra-secure type of environment variable. They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation. +Secrets are an extra-secure type of [environment variable]((/serverless-functions/concepts/#environment-variables). They are environment variables that are injected into your function and stored securely, but not displayed in the console after initial validation. Secrets defined at the function level override the ones defined at the namespace level if they have the same name. From c95b07ed4a16f03648eea3f114b291060e5f5d9b Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Fri, 13 Feb 2026 17:47:11 +0100 Subject: [PATCH 2/2] note about cockpit pricing --- pages/serverless-containers/how-to/monitor-container.mdx | 2 ++ pages/serverless-functions/how-to/monitor-function.mdx | 2 ++ pages/serverless-jobs/how-to/monitor-job.mdx | 2 ++ 3 files changed, 6 insertions(+) diff --git a/pages/serverless-containers/how-to/monitor-container.mdx b/pages/serverless-containers/how-to/monitor-container.mdx index 8ca33d8d7c..ec9803b6b1 100644 --- a/pages/serverless-containers/how-to/monitor-container.mdx +++ b/pages/serverless-containers/how-to/monitor-container.mdx @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx' Scaleway Serverless Containers is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Containers. +Logs and metrics for Serverless Containers with default retention (31 days for metrics / 7 days for logs & traces) are free of charge. + - A Scaleway account logged into the [console](https://console.scaleway.com) diff --git a/pages/serverless-functions/how-to/monitor-function.mdx b/pages/serverless-functions/how-to/monitor-function.mdx index dca9d1fdef..ca8235e4ee 100644 --- a/pages/serverless-functions/how-to/monitor-function.mdx +++ b/pages/serverless-functions/how-to/monitor-function.mdx @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx' Scaleway Serverless Functions is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Functions. +Logs and metrics for Serverless Jobs with default retention (31 days for metrics / 7 days for logs & traces) are free of charge. + Use your Cockpit logs and metrics to fine-tune the resources allocated to your Serverless Functions to avoid bottlenecks and over-provisioning. diff --git a/pages/serverless-jobs/how-to/monitor-job.mdx b/pages/serverless-jobs/how-to/monitor-job.mdx index 013a4d8e28..dbcc51bbf0 100644 --- a/pages/serverless-jobs/how-to/monitor-job.mdx +++ b/pages/serverless-jobs/how-to/monitor-job.mdx @@ -11,6 +11,8 @@ import Requirements from '@macros/iam/requirements.mdx' You can monitor the activity of your Serverless Jobs using the [Scaleway console](https://console.scaleway.com) to check the current status, RAM, and CPU consumption of your runs. Also, Serverless Jobs is fully integrated into Scaleway’s Observability [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs. +Logs and metrics for Serverless Jobs with default retention (31 days for metrics / 7 days for logs & traces) are free of charge. + - A Scaleway account logged into the [console](https://console.scaleway.com)