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. Users of the API, CLI, and Terraform must note several key updates to field names and behaviors.

This document only covers changes to Serverless Containers. The Serverless Functions and Serverless Jobs APIs remain unchanged.

Key improvements

Advanced Triggers and Cron management

Triggers have been redesigned to offer more granular control over how 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 (for example: /my-trigger) and custom headers for any trigger, providing better integration with application logic.
• 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, such as triggering a Scaleway container from an SQS queue hosted on your Instance.

Automatic Deployment

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.

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 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.

Health Checks

In addition to health checks, Startup Probes have been introduced. These 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.

A new field, timeout, allows customization of the duration before the check times out.

Breaking changes

When using the product via higher-level clients such as Scaleway Console, CLI, SDK, or Terraform, the impacts are minimal.

API field changes

To provide a seamless experience across all Scaleway products, the following fields have been updated: