Merge branch 'main' into MTA-5468

bene2k1 · web-flow · commit a87f1b582879 · 2025-01-14T10:18:37.000+01:00
diff --git a/compute/gpu/how-to/use-mig-with-kubernetes.mdx b/compute/gpu/how-to/use-mig-with-kubernetes.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This section provides information about MIG with Kubernetes
 tags: NVIDIA H100 MIG multi-instance gpu
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-09-19
 categories:
   - compute
diff --git a/compute/gpu/how-to/use-nvidia-mig-technology.mdx b/compute/gpu/how-to/use-nvidia-mig-technology.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This section provides information about NVIDIA's MIG technology
 tags: NVIDIA H100 MIG multi-instance gpu
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-08-31
 categories:
   - compute
diff --git a/compute/gpu/how-to/use-preinstalled-env.mdx b/compute/gpu/how-to/use-preinstalled-env.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to use the preinstalled environment
 tags: preinstalled environment preinstalled-environment gpu
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2022-03-25
 categories:
   - compute
@@ -41,7 +41,7 @@ Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation
     As Docker is also preinstalled, you could choose to [launch one of Scaleway's ready-made Docker images](/compute/gpu/how-to/use-gpu-with-docker/) to access our latest working environments, if you wish.
 3. Type `exit` to disconnect from your GPU Instance when you have finished your work.
 
-## Working with the preinstalled environment on Ubuntu Focal GPU OS 11
+## Working with the preinstalled environment on Ubuntu Focal GPU OS 12
 
 1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/).
 
diff --git a/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx b/compute/gpu/how-to/use-scratch-storage-h100-instances.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to use scratch storage on H100 and L40S GPU Instances
 tags: H100 L40S gpu scratch-storage scratch storage
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-09-18
 categories:
   - compute
diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx
@@ -34,10 +34,12 @@ Each method caters to different needs, balancing uninterrupted service against a
 | Instance API/CLI migration     | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost |
 | Snapshot export/import         | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling |
 
-
 This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage).
 Alternatively, you can use the [snapshot export/import feature](/compute/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes.
 
+
+<Macro id="block-storage-no-migration-for-k8s" />
+
 <Macro id="requirements" />
 
 - A Scaleway account logged into the [console](https://console.scaleway.com)
diff --git a/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx b/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx
@@ -35,6 +35,9 @@ You can either upgrade your Kubernetes Kapsule cluster [directly from the Scalew
     <Message type="note">
       It is not possible to downgrade your Kubernetes version once it has been upgraded.
     </Message>
+    <Message type="note">
+       Cluster pools cannot be resized during the upgrade process. Provision resources accordingly.
+    </Message>
 
 ## Upgrading a Kapsule cluster to the next minor version using the CLI
 
diff --git a/containers/kubernetes/how-to/use-scratch-storage-h100.mdx b/containers/kubernetes/how-to/use-scratch-storage-h100.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to use scratch storage with H100 and L40S GPUs and Kubernetes Kapsule
 tags: kubernetes kubernetes-kapsule kapsule cluster gpu-operator nvidia gpu scratch h100
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-12-27
 categories:
   - containers
diff --git a/identity-and-access-management/secret-manager/concepts.mdx b/identity-and-access-management/secret-manager/concepts.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Discover essential concepts of Scaleway Secret Manager, including secret versioning, ephemeral policies, and path management.
 tags: secret-manager secret version
 dates:
-  validation: 2024-07-10
+  validation: 2025-01-13
 ---
 
 ## Disabling a version
@@ -41,7 +41,7 @@ An ephemeral secret is a secret that has a limited lifetime, enforced by an [eph
 All the secret's versions automatically inherit their settings from those of the current ephemeral policy.
 
 <Message type="important">
- [Enabling](#enabling-a-version) a version that was previously [disabled](#disabling-a-version), amounts to recreating the version. If you have updated the secret's ephemeral policy while the version was disabled, enabling it again makes it inherit its settings from those of the current ephemeral policy.
+ [Enabling](#enabling-a-version) a version that was previously [disabled](#disabling-a-version) amounts to recreating the version. If you have updated the secret's ephemeral policy while the version was disabled, enabling it again makes it inherit its settings from those of the current ephemeral policy.
 </Message>
 
 ## Path
diff --git a/identity-and-access-management/secret-manager/how-to/create-secret.mdx b/identity-and-access-management/secret-manager/how-to/create-secret.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Discover how to efficiently create secrets using Scaleway's Secret Manager. Follow these step-by-step instructions whether you are setting up your first secret or adding more to your existing resources.
 tags: secret sensitive-data storage-system secret-type
 dates:
-  validation: 2024-07-10
+  validation: 2025-01-13
   posted: 2023-02-21
 categories:
   - identity-and-access-management
diff --git a/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx b/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to efficiently filter secrets by name, type, and tags with our detailed documentation, and enhance your security practices.
 tags: sensitive-data filter secret-type
 dates:
-  validation: 2024-07-10
+  validation: 2025-01-13
   posted: 2024-07-10
 categories:
   - identity-and-access-management
diff --git a/macros/storage/block-storage-no-migration-for-k8s.mdx b/macros/storage/block-storage-no-migration-for-k8s.mdx
@@ -0,0 +1,8 @@
+---
+macro: block-storage-no-migration-for-k8s
+---
+
+<Message type="important">
+ <br></br>
+  **Kubernetes customers must not migrate their block volumes to the Block Storage API to prevent major disruptions to their Kubernetes service and block volume unavailability.** You can identify your volumes by [listing them](/storage/block/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`.
+</Message>
diff --git a/managed-services/webhosting/how-to/configure-dns-webhosting.mdx b/managed-services/webhosting/how-to/configure-dns-webhosting.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Discover step-by-step instructions on configuring DNS settings for your web hosting, ensuring seamless connectivity and performance.
 tags: webhosting mx-record domain a-record aaaa-record
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-01-17
 categories:
   - managed-services
diff --git a/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx b/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to migrate an Online.net/Dedibox web hosting plan to Scaleway.
 tags: webhosting
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2023-09-18
 categories:
   - managed-services
diff --git a/managed-services/webhosting/how-to/order-webhosting.mdx b/managed-services/webhosting/how-to/order-webhosting.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to order a Scaleway Web Hosting with our detailed step-by-step guide.
 tags: webhosting order create
 dates:
-  validation: 2024-07-10
+  validation: 2025-01-25
   posted: 2023-01-17
 categories:
   - managed-services
@@ -24,7 +24,7 @@ This page shows how to create a Scaleway Web Hosting plan. Web Hosting is a mana
 1. Click **Web Hosting** in the **Managed Services** section of the side menu. This takes you to the Web Hosting dashboard.<br />
    If you already have Web Hosting plans, they will be listed. Click the **+ Order Web Hosting** button to add more plans.
 2. Click **Order Web Hosting** to start the creation process.
-3. Select a **region** and a **control panel** for your Web Hosting plan. 
+3. Select a **region** and a **control panel** for your Web Hosting plan.
      * You can choose between:
        * **cPanel**: A web-based control panel for managing web hosting accounts, emails, and websites through a graphical interface.
        * **Plesk**: A user-friendly web hosting control panel for managing websites, emails, and hosting accounts.
diff --git a/storage/block/reference-content/advantages-migrating-to-sbs.mdx b/storage/block/reference-content/advantages-migrating-to-sbs.mdx
@@ -15,9 +15,7 @@ categories:
 
 This page explains why **Instance users** should migrate from the Instance API to the Block Storage API to create and manage block volumes and snapshots.
 
-<Message type="important">
-  The information displayed on this page **does not apply to Kapsule users with persistent block volumes**. You can identify them by [listing your volumes](/storage/block/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`.
-</Message>
+<Macro id="block-storage-no-migration-for-k8s" />
 
 ## Transitioning from the Instance API to the Block Storage API for volume and snapshot management
 
diff --git a/tutorials/manage-zigbee-devices-with-iot/index.mdx b/tutorials/manage-zigbee-devices-with-iot/index.mdx
@@ -9,7 +9,7 @@ categories:
   - iot-hub
 tags: iot iot-hub zigbee zigbee2mqtt
 dates:
-  validation: 2024-07-08
+  validation: 2025-01-13
   posted: 2022-12-20
 ---
 
@@ -38,11 +38,11 @@ Zigbee2MQTT is configured using YAML based `configuration.yaml` file. Modify thi
   ```
   # Required: MQTT settings
   mqtt:
-    server: mqtts://iot.fr-par.scw.cloud:8883
+    server: mqtts://iot.fr-par.scw.cloud:8883 # mqtts endpoint
     base_topic: zigbee2mqtt
-    ca: /etc/ssl/mqtt-ca.crt
-    key: /etc/ssl/mqtt-client.key
-    cert: /etc/ssl/mqtt-client.crt
+    ca: /etc/ssl/mqtt-ca.crt                  # Certificate Authority
+    key: /etc/ssl/mqtt-client.key             # Device private key
+    cert: /etc/ssl/mqtt-client.crt            # Device certificate
     client_id: <Device_ID>
     keepalive: 60
     version: 4
