Merge branch 'scaleway:main' into main

Author: enzzc

changelog/may2025/2025-05-07-containers-added-request-timeout-up-to-1h.mdx

@@ -0,0 +1,14 @@
+---
+title: Maximum request timeout increased to one hour
+status: added
+date: 2025-05-07
+category: serverless
+product: containers
+---
+
+Serverless Containers now support a request timeout of up to one hour. This significant increase in timeout duration opens up new possibilities for long-running tasks and workloads. With this update, you can now use Serverless Containers for a wider range of use cases, such as: 
+* Running complex data processing tasks that require extended execution times
+* Hosting long-running webhooks or callbacks that need to handle prolonged requests
+* Supporting real-time data streaming applications that require continuous processing
+* Enabling wider usage of websockets
+

changelog/may2025/2025-05-07-functions-added-request-timeout-up-to-1h.mdx

@@ -0,0 +1,14 @@
+---
+title: Maximum request timeout raised to one hour
+status: added
+date: 2025-05-07
+category: serverless
+product: functions
+---
+
+Serverless Functions now support a request timeout of up to one hour. This significant increase in timeout duration opens up new possibilities for long-running tasks and workloads. With this update, you can now use Serverless Functions for a wider range of use cases, such as: 
+* Running complex data processing tasks that require extended execution times
+* Hosting long-running webhooks or callbacks that need to handle prolonged requests
+* Supporting real-time data streaming applications that require continuous processing
+* Enabling wider usage of websockets
+

changelog/may2025/2025-05-12-webhosting-removed-plesk-option-removed.mdx

@@ -0,0 +1,9 @@
+---
+title: Plesk option removed
+status: removed
+date: 2025-05-12
+category: managed-services
+product: webhosting
+---
+
+To streamline our Web Hosting offer, the Plesk option has been removed for new orders. Existing web hostings with Plesk remain fully functional and supported. However, we encourage users to explore alternative solutions available in the [Scaleway console](https://console.scaleway.com/webhosting) for new deployments.

menu/navigation.json

@@ -1235,6 +1235,10 @@
                     "label": "Shut down a server",
                     "slug": "shutdown-server"
                   },
+                  {
+                    "label": "Change the billing period",
+                    "slug": "change-billing-period"
+                  },
                   {
                     "label": "Get and use a loyalty reward",
                     "slug": "get-use-loyalty-reward"
@@ -3789,6 +3793,10 @@
                   {
                     "label": "Cockpit capabilities and limits",
                     "slug": "cockpit-limitations"
+                  },
+                  {
+                    "label": "Cockpit supported API endpoints for data source management",
+                    "slug": "cockpit-supported-endpoints"
                   }
                 ],
                 "label": "Additional Content",
@@ -3929,6 +3937,10 @@
                     "label": "Functions autoscaling",
                     "slug": "functions-autoscaling"
                   },
+                  {
+                    "label": "Functions sandbox",
+                    "slug": "functions-sandbox"
+                  },
                   {
                     "label": "Code examples",
                     "slug": "code-examples"
@@ -4097,6 +4109,10 @@
                     "label": "Containers port parameter",
                     "slug": "port-parameter-variable"
                   },
+                  {
+                    "label": "Containers sandbox",
+                    "slug": "containers-sandbox"
+                  },
                   {
                     "label": "Differences between Jobs, Functions and Containers",
                     "slug": "difference-jobs-functions-containers"

package.json

@@ -21,10 +21,10 @@
     ]
   },
   "devDependencies": {
-    "@commitlint/cli": "^19.8.0",
-    "@commitlint/config-conventional": "^19.8.0",
+    "@commitlint/cli": "^19.8.1",
+    "@commitlint/config-conventional": "^19.8.1",
     "husky": "^8.0.3",
-    "lint-staged": "^15.5.1",
+    "lint-staged": "^16.0.0",
     "prettier": "^3.5.3"
   },
   "scripts": {

pages/cockpit/reference-content/cockpit-supported-endpoints.mdx

@@ -0,0 +1,169 @@
+---
+meta:
+  title: Cockpit supported API endpoints for data source management
+  description: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir, Loki, Tempo and Prometheus endpoints
+content:
+  h1: Cockpit supported API endpoints for data source management
+  paragraph: Discover how to manage your telemetry data sources using the Scaleway-supported Mimir, Loki, Tempo and Prometheus endpoints
+tags: observability cockpit endpoints mimir loki telemetry prometheus tempo datasource-management
+dates:
+  validation: 2025-05-05
+  posted: 2025-05-05
+categories:
+  - observability
+---
+
+Cockpit supports telemetry ingestion and querying using the following open-source technologies:
+
+- [Mimir](https://grafana.com/oss/mimir/) for metrics
+- [Loki](https://grafana.com/oss/loki/) for logs
+- [Tempo](https://grafana.com/oss/tempo/) for traces
+- [Prometheus](https://prometheus.io/docs/alerting/latest/alertmanager/) for the alert manager
+
+Cockpit exposes a subset of their HTTP APIs so users can push, query, and manage telemetry data from Cockpit.
+
+    <Message type="important">
+     Scaleway does not support all endpoints from these upstream APIs. Refer to the exact lists below to find out which endpoints are supported.
+    </Message>
+
+<Macro id="requirements" />
+
+  - A Scaleway account logged into the [console](https://console.scaleway.com)
+  - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization or Project
+  - [Created](/cockpit/how-to/create-token/) a Cockpit token with the right [permissions](/cockpit/concepts/#cockpit-tokens)
+  - Retrieved the URL of your data source from the [Scaleway console](https://console.scaleway.com/cockpit/dataSource) or the [API](https://www.scaleway.com/en/developers/api/cockpit/regional-api/#path-data-sources-list-data-sources)
+
+## Mimir supported endpoints (metrics)
+
+The base URL pattern for metrics is the following: `https://<data-source-id>.metrics.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).
+
+Refer to the [official Mimir documentation](https://grafana.com/docs/mimir/latest/references/http-api/) for more details about the endpoints below.
+
+<Concept>
+  ## Mimir write endpoints
+
+    Method: `POST`.
+
+    - Path: `/api/v1/push`
+    - Path: `/otlp/v1/metrics`
+</Concept>
+
+<Concept>
+  ## Mimir query endpoints
+
+    Methods: `GET` and `POST`.
+
+    - Path: `/prometheus/api/v1/query`
+    - Path: `/prometheus/api/v1/query_range`
+    - Path: `/prometheus/api/v1/query_exemplars`
+    - Path: `/prometheus/api/v1/series`
+    - Path: `/prometheus/api/v1/labels`
+    - Path: `/prometheus/api/v1/label/*`
+    - Path: `/prometheus/api/v1/metadata`
+    - Path: `/prometheus/api/v1/read`
+    - Path: `/prometheus/api/v1/status/buildinfo`
+</Concept>
+
+<Concept>
+  ## Mimir rules endpoints
+
+    Methods: `GET`, `POST`, and `DELETE`.
+
+    - Path: `/prometheus/api/v1/rules`
+    - Path: `/prometheus/api/v1/alerts`
+    - Path: `/prometheus/config/v1/rules`
+    - Path: `/prometheus/config/v1/rules/*`
+</Concept>
+
+
+## Loki supported endpoints (logs)
+
+The base URL pattern for logs is the following: `https://<data-source-id>.logs.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).
+
+Refer to the [official Loki documentation](https://grafana.com/docs/loki/latest/reference/loki-http-api/) for more details about the endpoints below.
+
+<Concept>
+  ## Loki write endpoints
+
+    Method: `POST`.
+
+    - Path: `/loki/api/v1/push`
+    - Path: `/otlp/v1/logs`
+</Concept>
+
+<Concept>
+  ## Loki query endpoints
+
+    Methods: `GET` and `POST`.
+
+    - Path: `/loki/api/v1/query`
+    - Path: `/loki/api/v1/query_range`
+    - Path: `/loki/api/v1/labels`
+    - Path: `/loki/api/v1/label`
+    - Path: `/loki/api/v1/label/*`
+    - Path: `/loki/api/v1/tail`
+    - Path: `/loki/api/v1/series`
+</Concept>
+
+<Concept>
+  ## Loki rules endpoints
+
+    Methods: `GET`, `POST`, and `DELETE`.
+
+    - Path: `/loki/api/v1/rules`
+    - Path: `/loki/api/v1/rules/*`
+    - Path: `/api/prom/rules`
+    - Path: `/api/prom/rules/*`
+    - Path: `/prometheus/api/v1/rules`
+    - Path: `/prometheus/api/v1/alerts`
+</Concept>
+
+## Tempo supported endpoints (traces)
+
+The base URL pattern for traces is the following: `https://<data-source-id>.traces.cockpit.<region>.scw.cloud`. You must replace `<data-source-id>` with the ID of your data source and `<region>` with the region where your data source is located (`fr-par`, `nl-ams`, or `pl-waw`).
+
+Refer to the [official Tempo documentation](https://grafana.com/docs/tempo/latest/api_docs/) for more details about the endpoints below.
+
+<Concept>
+  ## Tempo write endpoints
+
+    Method: `POST`.
+
+    - Path: `/otlp/v1/traces`
+    - Path: `/opentelemetry.proto.collector.trace.v1.TraceService/Export`
+    - Path: `/jaeger`
+    - Path: `/zipkin`
+</Concept>
+
+<Concept>
+  ## Tempo query endpoints
+
+    Method: `GET`.
+
+    - Path: `/api/echo`
+    - Path: `/api/traces/*`
+    - Path: `/api/search`
+    - Path: `/api/search/tags`
+    - Path: `/api/v2/search/tags`
+    - Path: `/api/search/tag/*/values`
+    - Path: `/api/v2/search/tag/*/values`
+</Concept>
+
+## Prometheus alert manager supported endpoints
+
+The base URL pattern for the alert manager is the following: `https://<alert-manager-id>.alertmanager.cockpit.<region>.scw.cloud`. You must replace `<alert-manager-id>` with the ID of your alert manager and `<region>` with the region where the alert manager is enabled (`fr-par`, `nl-ams`, or `pl-waw`).
+
+Refer to the [official Prometheus alert manager documentation](https://prometheus.io/docs/prometheus/latest/querying/api/#alerts) for more details about the endpoints below.
+
+<Message type="important">
+  You must use the [Cockpit API](https://www.scaleway.com/en/developers/api/cockpit/regional-api/#path-alert-manager-get-the-alert-manager) to retrieve the ID of the alert manager.
+</Message>
+
+<Concept>
+  ## Alert manager endpoints
+
+    Methods: `GET`, `POST`, and `DELETE`.
+
+    - Path: `/alertmanager/*`
+    - Path: `/api/v1/alerts`
+</Concept>

pages/elastic-metal/how-to/change-billing-period.mdx

@@ -0,0 +1,37 @@
+---
+meta:
+  title: How to change the billing period for Elastic Metal Servers
+  description: This page explains how to change the billing period for Scaleway's Elastic Metal servers.
+content:
+  h1: How to change the billing period for Elastic Metal Servers
+  paragraph: This page explains how to change the billing period for Scaleway's Elastic Metal servers.
+  tags: apple-silicon elastic-metal
+  dates:
+    validation: 2025-03-12
+    posted: 2025-03-12
+  categories:
+    - bare-metal
+---
+
+Scaleway's Elastic Metal servers offer flexible billing options to suit your needs. If you are currently using hourly billing, you can upgrade to monthly billing directly from the Scaleway console.
+By switching to monthly billing, you can benefit from significant discounts compared to the hourly pricing model.
+This provides you with cost savings for longer-term server rentals and allows you to retain your existing server configuration without requiring a new setup.
+
+<Macro id="requirements" />
+- A Scaleway account logged into the [console](https://console.scaleway.com)
+- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization
+- An [Elastic Metal server](/bare-metal/how-to/create-server/)
+
+1. Click [Elastic Metal](https://console.scaleway.com/elastic-metal/servers) in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays.
+2. Click the server you want to configure. The server's information page displays.
+3. Scroll down to the **Billing preferences** section. Here, you can see information about your current billing option. Click **Update to monthly billing**. A pop-up displays.
+4. Review the server and optipons details and their new monthly pricing. Note that switching to monthly billing incurs a one-time commitment fee, which is charged immediately.
+    <Message type="important">
+        - Once switched to monthly billing, reverting to hourly billing is not possible.
+        - A commitment fee is due immediately upon switching. This fee can be redeemed after 12 months as a voucher for other Scaleway services. [Learn more.](/elastic-metal/how-to/get-use-loyalty-reward/)
+    </Message>
+5. Tick the checkbox to acknowledge that the commitment fee will be debited immediately upon upgrading.
+6. Confirm the new billing period by clicking **Update billing**.
+    <Message type="note">
+      Switching from hourly to monthly may take a few minutes, during which the server will be in a `migrating` state.
+    </Message>

pages/elastic-metal/how-to/create-server.mdx

@@ -33,6 +33,9 @@ Scaleway [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) pro
         - Warsaw, Poland (`WAW-2`, `WAW-3`)
       </Message>
     - Choose your preferred billing method: **hourly** or **monthly**.
+      <Message type="tip">
+        You can update the billing period to monthly at any time after your server has been delivered. [Learn more.](/elastic-metal/how-to/change-billing-period/)
+      </Message>
     - Select a server configuration from the available options.
     - Choose an OS to run on your server or opt for no preinstalled image.
     - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/).

pages/elastic-metal/how-to/use-private-networks.mdx

@@ -65,7 +65,7 @@ You can also attach custom resources, such as virtual machines hosted on your El
     - Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create.
     <Message type="note">
     The Private Network will have default settings, meaning:
-      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region
+      - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. If you do not have an existing VPC for the appropriate region, one will be auto-created for you
       - It has an auto-generated [CIDR block](/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network.
     </Message>
 6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network.

pages/elastic-metal/quickstart.mdx

@@ -34,6 +34,9 @@ Scaleway Elastic Metal are dedicated physical servers you can order on-demand, l
         - Warsaw, Poland (`WAW-2`, `WAW-3`)
       </Message>
     - Choose your preferred billing method: **hourly** or **monthly**.
+      <Message type="tip">
+        You can update the billing period to monthly at any time after your server has been delivered. [Learn more.](/elastic-metal/how-to/change-billing-period/)
+      </Message>
     - Select a server configuration from the available options.
     - Choose an OS to run on your server or opt for no preinstalled image.
     - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration.