Status impact color legend
- Black impact: None
- Yellow impact: Minor
- Red impact: Major
- Blue impact: Maintenance
[Serverless Containers] - [nl-ams] - mandatory operation to prepare for new v1 API
Scheduled for Mar 2, 08:00 CET - Mar 3, 17:00 CET
Subscribe to Updates
Scheduled
On March 2nd and 3rd (between 8 AM and 5 PM UTC), we are going to perform on nl-ams a required operation to prepare the new v1 API arrival (available soon).
During this operation, changes will be performed to all Serverless Containers namespaces on nl-ams region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual.
- Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out Container instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.
Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable.
This process is mandatory to prepare a seamless upgrade to the new v1 API (coming soon, with new features!).
Thanks for your understanding and sorry about the inconvenience it may cause.
During this operation, changes will be performed to all Serverless Containers namespaces on nl-ams region.
While this operation is seamless most of the time, users may observe the following behaviors:
- Namespaces will pass temporarily in "upgrading" status. This may take up to 15 minutes, depending on the number of resources inside the namespace. During this time, all write operations on the namespace (update namespace, create container, update container, delete container, etc.) will be impossible. Read operations will work as usual.
- Container instances will be created. This is mandatory to ensure the containers are working properly. If a container fails to start, the "status" field will change to "error", and the "error_message" field will show the error, so users can fix it. During that process, users could see multiple instances of their container running, even if it's configured with max_scale = 1, and even if there is no incoming traffic. The Container will downscale as soon as the operation is over.
- Long running requests made during this operation may fail, as we roll out Container instances.
- Crons might be triggered multiple times during the operation. Crons with frequent schedules (such as every minute) might be more impacted.
Please note that during this process, unless the containers cannot start because of an applicative error, the containers will always be reachable.
This process is mandatory to prepare a seamless upgrade to the new v1 API (coming soon, with new features!).
Thanks for your understanding and sorry about the inconvenience it may cause.
This scheduled maintenance affects: Elements - AZ (nl-ams-1, nl-ams-2, nl-ams-3) and Elements - Products (Serverless Functions and Containers).