From b93fab6dec21e2e8980a09c248aced23ef32acc2 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Mon, 9 Feb 2026 18:00:00 +0100 Subject: [PATCH 1/4] feat(containers): v1 api --- .../reference-content/v1-migration-guide.mdx | 62 +++++++++++++++++++ 1 file changed, 62 insertions(+) create mode 100644 pages/serverless-containers/reference-content/v1-migration-guide.mdx diff --git a/pages/serverless-containers/reference-content/v1-migration-guide.mdx b/pages/serverless-containers/reference-content/v1-migration-guide.mdx new file mode 100644 index 0000000000..3c40e26191 --- /dev/null +++ b/pages/serverless-containers/reference-content/v1-migration-guide.mdx @@ -0,0 +1,62 @@ +--- +title: Serverless Containers v1beta1 to v1 +description: Discover the new features and changes introduced in the Serverless Containers v1 API. +tags: containers serverless-containers migration api v1 serverless +dates: + validation: 2026-02-09 + posted: 2026-02-09 +--- + +# Overview of the v1 API evolution + +The transition from `v1beta1` to `v1` for Scaleway Serverless Containers introduces significant improvements in security, resource management, and flexibility. +While the transition is designed to be as smooth as possible, users of the API, CLI, and Terraform should note several key updates to field names and behaviors. + + + Please be careful for `Breaking changes` mentions. + + +## Key improvements + +### Advanced Triggers and Cron management + +Triggers have been redesigned to offer more granular control over how your containers are invoked. + +* **Unified CRONs:** CRONs are now managed as a specific type of trigger. This simplifies resource management by using the /triggers route for all event sources. +* **Custom HTTP paths and headers:** You can now specify a custom HTTP path (ex: `/my-trigger`) and custom headers for any trigger, providing better integration with your application logic. +* Self-managed credentials: For SQS and NATS triggers, you now provide your own IAM credentials. This improvement prevents accidental trigger failures caused by deleted system-generated credentials and enables more freedom on setups (triggering a Scaleway container from SQS queue hosted on your Instance). + +### Automatic Deployment + +In the `v1` API, the `deploy = true` flag is no longer required. Any call to `CreateContainer` or an update will now automatically deploy the container immediately. This aligns Serverless Containers with the standard behavior of all other Scaleway products. + +## Container Registry namespaces + +Creating a Serverless Containers namespace no longer creates a `funcscw` Container Registry namespace automatically. + +This change allows for greater control over the organization or Container Reigstry namespaces, and avoids quota errors when creating Container Namespaces. + +## Healthchecks + +In addition to health checks, we have introduced Startup Probes. This allows advanced users to define a specific check that runs only during the initial boot of the container, preventing the system from prematurely restarting slow-starting applications. + +## Breaking changes + + **Attention required:** Breaking change. If you call Scaleway Serverless Containers API directly, via HTTP calls you need to be careful on the following modifications. + +When using the product via higer level clients like [Scaleway Console](https://console.scaleway.com/), [CLI](https://github.com/scaleway/scaleway-cli), [SDK](https://www.scaleway.com/en/docs/scaleway-sdk/), +[Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) the impacts will be minor. + +### API names changes + +In order to provide a more integrated experience trough our Scaleway products, please check the following table: + +| `v1beta1` name | `v1` name | Unit change | Notes | +| ------------------------- | --------------------------- | --------------- | -------------------------------------------- | +| `memory_limit` | `memory_limit_bytes` | ⚠️ MiB to Bytes | | +| `local_storage_limit` | `local_storage_limit_bytes` | ⚠️ MiB to Bytes | | +| `domain_name` | `public_endpoint` | N/A | To differentiate public en private endpoints | +| `health_check` | `liveness_probe` | N/A | Was a readiness probe in `v1beta1` | +| `cpu_limit` | `mvcpu_limit` | N/A | Precision of the unit | +| `http_option: Redirected` | `https_connections_only` | N/A | Now a boolean value | + From 158ed9014f5565544b8b5f34bbf4864ee3b383c5 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Mon, 9 Feb 2026 21:17:00 +0100 Subject: [PATCH 2/4] typos --- .../reference-content/v1-migration-guide.mdx | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/pages/serverless-containers/reference-content/v1-migration-guide.mdx b/pages/serverless-containers/reference-content/v1-migration-guide.mdx index 3c40e26191..b0bb4904f1 100644 --- a/pages/serverless-containers/reference-content/v1-migration-guide.mdx +++ b/pages/serverless-containers/reference-content/v1-migration-guide.mdx @@ -13,7 +13,7 @@ The transition from `v1beta1` to `v1` for Scaleway Serverless Containers introdu While the transition is designed to be as smooth as possible, users of the API, CLI, and Terraform should note several key updates to field names and behaviors. - Please be careful for `Breaking changes` mentions. + Please pay attention to `Breaking changes` mentions. ## Key improvements @@ -34,22 +34,22 @@ In the `v1` API, the `deploy = true` flag is no longer required. Any call to `Cr Creating a Serverless Containers namespace no longer creates a `funcscw` Container Registry namespace automatically. -This change allows for greater control over the organization or Container Reigstry namespaces, and avoids quota errors when creating Container Namespaces. +This change allows for greater control over the organization of Container Registry namespaces, and avoids quota errors when creating Container Namespaces. -## Healthchecks +## Health Checks In addition to health checks, we have introduced Startup Probes. This allows advanced users to define a specific check that runs only during the initial boot of the container, preventing the system from prematurely restarting slow-starting applications. ## Breaking changes - **Attention required:** Breaking change. If you call Scaleway Serverless Containers API directly, via HTTP calls you need to be careful on the following modifications. +**Attention required:** Breaking change. If you call Scaleway Serverless Containers API directly via HTTP calls, you need to be careful about the following modifications. -When using the product via higer level clients like [Scaleway Console](https://console.scaleway.com/), [CLI](https://github.com/scaleway/scaleway-cli), [SDK](https://www.scaleway.com/en/docs/scaleway-sdk/), +When using the product via higher level clients like [Scaleway Console](https://console.scaleway.com/), [CLI](https://github.com/scaleway/scaleway-cli), [SDK](https://www.scaleway.com/en/docs/scaleway-sdk/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) the impacts will be minor. ### API names changes -In order to provide a more integrated experience trough our Scaleway products, please check the following table: +In order to provide a more integrated experience through our Scaleway products, please check the following table: | `v1beta1` name | `v1` name | Unit change | Notes | | ------------------------- | --------------------------- | --------------- | -------------------------------------------- | From 394b651d92a2df17d8dbd9dfad295931a1000018 Mon Sep 17 00:00:00 2001 From: Thomas Tacquet Date: Tue, 10 Feb 2026 10:57:13 +0100 Subject: [PATCH 3/4] small precisions --- .../reference-content/v1-migration-guide.mdx | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/pages/serverless-containers/reference-content/v1-migration-guide.mdx b/pages/serverless-containers/reference-content/v1-migration-guide.mdx index b0bb4904f1..4a7a30334d 100644 --- a/pages/serverless-containers/reference-content/v1-migration-guide.mdx +++ b/pages/serverless-containers/reference-content/v1-migration-guide.mdx @@ -12,6 +12,8 @@ dates: The transition from `v1beta1` to `v1` for Scaleway Serverless Containers introduces significant improvements in security, resource management, and flexibility. While the transition is designed to be as smooth as possible, users of the API, CLI, and Terraform should note several key updates to field names and behaviors. +Scope of this document is only for Serverless Containers. Serverless Functions and Serverless Jobs API remains the same. + Please pay attention to `Breaking changes` mentions. @@ -24,19 +26,23 @@ Triggers have been redesigned to offer more granular control over how your conta * **Unified CRONs:** CRONs are now managed as a specific type of trigger. This simplifies resource management by using the /triggers route for all event sources. * **Custom HTTP paths and headers:** You can now specify a custom HTTP path (ex: `/my-trigger`) and custom headers for any trigger, providing better integration with your application logic. -* Self-managed credentials: For SQS and NATS triggers, you now provide your own IAM credentials. This improvement prevents accidental trigger failures caused by deleted system-generated credentials and enables more freedom on setups (triggering a Scaleway container from SQS queue hosted on your Instance). +* **Self-managed credentials:** For SQS and NATS triggers, you now provide your own IAM credentials. This improvement prevents accidental trigger failures caused by deleted system-generated credentials and enables more freedom on setups (triggering a Scaleway container from SQS queue hosted on your Instance). ### Automatic Deployment In the `v1` API, the `deploy = true` flag is no longer required. Any call to `CreateContainer` or an update will now automatically deploy the container immediately. This aligns Serverless Containers with the standard behavior of all other Scaleway products. -## Container Registry namespaces +### Auth with IAM + +JWT auth is being gradually deprecated in favor of IAM tokens. The deprecation will be effective once IAM tokens can provide the same granularity of JWT. [Read more](/serverless-functions/how-to/migrate-jwt-to-iam-authentication/). + +### Container Registry namespaces Creating a Serverless Containers namespace no longer creates a `funcscw` Container Registry namespace automatically. This change allows for greater control over the organization of Container Registry namespaces, and avoids quota errors when creating Container Namespaces. -## Health Checks +### Health Checks In addition to health checks, we have introduced Startup Probes. This allows advanced users to define a specific check that runs only during the initial boot of the container, preventing the system from prematurely restarting slow-starting applications. @@ -47,7 +53,7 @@ In addition to health checks, we have introduced Startup Probes. This allows adv When using the product via higher level clients like [Scaleway Console](https://console.scaleway.com/), [CLI](https://github.com/scaleway/scaleway-cli), [SDK](https://www.scaleway.com/en/docs/scaleway-sdk/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) the impacts will be minor. -### API names changes +### API field changes In order to provide a more integrated experience through our Scaleway products, please check the following table: From e5b1088ec20a7dcdd8369300073498bc50b0e8f5 Mon Sep 17 00:00:00 2001 From: Thomas TACQUET Date: Tue, 10 Feb 2026 21:30:49 +0100 Subject: [PATCH 4/4] Apply suggestions from code review MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: SamyOubouaziz Co-authored-by: Jessica <113192637+jcirinosclwy@users.noreply.github.com> Co-authored-by: Andy Méry --- .../reference-content/v1-migration-guide.mdx | 30 ++++++++++--------- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/pages/serverless-containers/reference-content/v1-migration-guide.mdx b/pages/serverless-containers/reference-content/v1-migration-guide.mdx index 4a7a30334d..3672e0dcd6 100644 --- a/pages/serverless-containers/reference-content/v1-migration-guide.mdx +++ b/pages/serverless-containers/reference-content/v1-migration-guide.mdx @@ -12,10 +12,10 @@ dates: The transition from `v1beta1` to `v1` for Scaleway Serverless Containers introduces significant improvements in security, resource management, and flexibility. While the transition is designed to be as smooth as possible, users of the API, CLI, and Terraform should note several key updates to field names and behaviors. -Scope of this document is only for Serverless Containers. Serverless Functions and Serverless Jobs API remains the same. +The changes outlined in this document only concern Serverless Containers. The Serverless Functions and Serverless Jobs APIs remains the same. - Please pay attention to `Breaking changes` mentions. + Be mindful of the `Breaking changes` mentions. ## Key improvements @@ -24,44 +24,46 @@ Scope of this document is only for Serverless Containers. Serverless Functions a Triggers have been redesigned to offer more granular control over how your containers are invoked. -* **Unified CRONs:** CRONs are now managed as a specific type of trigger. This simplifies resource management by using the /triggers route for all event sources. +* **Unified CRONs:** CRONs are now managed as a specific type of trigger. This simplifies resource management by using the `/triggers` route for all event sources. * **Custom HTTP paths and headers:** You can now specify a custom HTTP path (ex: `/my-trigger`) and custom headers for any trigger, providing better integration with your application logic. -* **Self-managed credentials:** For SQS and NATS triggers, you now provide your own IAM credentials. This improvement prevents accidental trigger failures caused by deleted system-generated credentials and enables more freedom on setups (triggering a Scaleway container from SQS queue hosted on your Instance). +* **Self-managed credentials:** For SQS and NATS triggers, you must now provide your own IAM credentials. This improvement prevents accidental trigger failures caused by deleted system-generated credentials, and enables more flexibility (triggering a Scaleway container from SQS queue hosted on your Instance). ### Automatic Deployment -In the `v1` API, the `deploy = true` flag is no longer required. Any call to `CreateContainer` or an update will now automatically deploy the container immediately. This aligns Serverless Containers with the standard behavior of all other Scaleway products. +In the `v1` API, the `deploy = true` flag is no longer required. `CreateContainer` API calls and container updates will now automatically deploy the container immediately. This aligns Serverless Containers with the standard behavior of all other Scaleway products. -### Auth with IAM +### IAM Authentication -JWT auth is being gradually deprecated in favor of IAM tokens. The deprecation will be effective once IAM tokens can provide the same granularity of JWT. [Read more](/serverless-functions/how-to/migrate-jwt-to-iam-authentication/). +JWT-based authentication is being gradually deprecated in favor of IAM credentials. The deprecation will be effective once IAM credentials provide the same granularity as JWTs. Refer to the [dedicated documentation](/serverless-functions/how-to/migrate-jwt-to-iam-authentication/) for more information. ### Container Registry namespaces Creating a Serverless Containers namespace no longer creates a `funcscw` Container Registry namespace automatically. -This change allows for greater control over the organization of Container Registry namespaces, and avoids quota errors when creating Container Namespaces. +This change allows for greater control over the organization of Container Registry namespaces, and avoids quota errors when creating Container namespaces. ### Health Checks -In addition to health checks, we have introduced Startup Probes. This allows advanced users to define a specific check that runs only during the initial boot of the container, preventing the system from prematurely restarting slow-starting applications. +In addition to health checks, we have introduced Startup Probes. They allow advanced users to define a specific check that runs only during the initial boot of the container, preventing the system from prematurely restarting slow-starting applications. ## Breaking changes -**Attention required:** Breaking change. If you call Scaleway Serverless Containers API directly via HTTP calls, you need to be careful about the following modifications. + +If you call the Scaleway Serverless Containers API directly via HTTP calls, you must pay attention to the following breaking changes. + When using the product via higher level clients like [Scaleway Console](https://console.scaleway.com/), [CLI](https://github.com/scaleway/scaleway-cli), [SDK](https://www.scaleway.com/en/docs/scaleway-sdk/), [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) the impacts will be minor. ### API field changes -In order to provide a more integrated experience through our Scaleway products, please check the following table: +In order to provide a seamless experience across all Scaleway products, we updated the following fields: | `v1beta1` name | `v1` name | Unit change | Notes | | ------------------------- | --------------------------- | --------------- | -------------------------------------------- | -| `memory_limit` | `memory_limit_bytes` | ⚠️ MiB to Bytes | | -| `local_storage_limit` | `local_storage_limit_bytes` | ⚠️ MiB to Bytes | | -| `domain_name` | `public_endpoint` | N/A | To differentiate public en private endpoints | +| `memory_limit` | `memory_limit_bytes` | MiB to Bytes | | +| `local_storage_limit` | `local_storage_limit_bytes` | MiB to Bytes | | +| `domain_name` | `public_endpoint` | N/A | To differentiate public and private endpoints | | `health_check` | `liveness_probe` | N/A | Was a readiness probe in `v1beta1` | | `cpu_limit` | `mvcpu_limit` | N/A | Precision of the unit | | `http_option: Redirected` | `https_connections_only` | N/A | Now a boolean value |