scaleway · ldecarvalho-doc · Dec 24, 2024 · Dec 23, 2024
@@ -7,7 +7,7 @@ content:
   paragraph: Discover a complete list of OS images and InstantApps available for Scaleway Instances. Choose the perfect setup for your needs and optimize your virtual environment.
 tags: instance
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2024-06-17
 categories:
   - compute

@@ -7,7 +7,7 @@ content:
   paragraph: This page helps you to fix the PPA configuration on Ubuntu 24.04 Noble
 tags: ubuntu-noble noble 24.04 ppa staging
 dates:
-  validation: 2024-06-20
+  validation: 2024-12-23
   posted: 2024-06-20
 categories:
   - compute

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to push container images to Scaleway's Container Registry.
 tags: push-image namespace container-registry
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2019-02-25
 categories:
   - container-registry

@@ -7,7 +7,7 @@ content:
   paragraph: Monitoring of your Kubernetes Kapsule cluster
 tags: kubernetes cluster pvc
 dates:
-  validation: 2024-06-20
+  validation: 2024-12-23
   posted: 2020-10-14
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to manage your Scaleway Kubernetes Kapsule cluster, including adding nodes and pools via the Scaleway console.
 tags: kubernetes kapsule-cluser
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-05-31
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to manage your Scaleway Kubernetes Kosmos cluster, including adding nodes and pools via the Scaleway console.
 tags: kubernetes kosmos-cluster kosmos
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-05-31
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to deploy containerized applications with the Easy Deploy feature on Scaleway Kubernetes clusters.
 tags: deploy containerized-applications easy-deploy
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2020-10-14
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Discover step-by-step instructions on upgrading the Kubernetes version for your Kapsule cluster to ensure optimal performance and features.
 tags: kubernetes kubernetes-kapsule kapsule cluster upgrade
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2022-12-21
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Explore the basics of Kubernetes (K8s), an open-source platform for managing containerized workloads and services.
 tags: kubernetes persistent volume persistent-volume
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-05-31
 categories:
   - kubernetes

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to resolve connection problems with your email account on Web Hosting Classic quickly and easily.
 tags: webhosting connection problem error email
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-05-26
 categories:
   - webhosting

@@ -7,7 +7,7 @@ content:
   paragraph: This page shows you how to get started with cPanel webhosting.
 tags: webhosting cpanel
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-05-26
 categories:
   - webhosting
@@ -58,6 +58,6 @@ Nameservers are servers used to translate domain names into IP addresses. When y
     <Lightbox src="scaleway_list_of_domains.webp" alt="" />
     <Lightbox src="scaleway_status_of_domain_names.webp" alt="" />
 3. Click the **Manage DNS Servers** tab to find a list of your nameservers.
-4. Erase the old addresses. 
+4. Erase the old addresses.
 5. Include the new cPanel nameservers.
 6. Click **Update DNS Servers** to update the information.
@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to use the KVM device of Quanta Computer servers on Scaleway dedicated servers
 tags: kvm quanta qct
 dates:
-  validation: 2024-06-17
+  validation: 2024-12-23
   posted: 2021-07-16
 categories:
   - dedibox-servers

diff --git a/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx b/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx
@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to effectively monitor your Database Instance using Scaleway Cockpit for optimal performance.
 tags:  managed-database database cockpit observability dashboard metrics logs alerts
 dates:
-  validation: 2024-06-19
+  validation: 2024-12-23
   posted: 2024-06-19
 categories:
   - managed-databases

@@ -8,7 +8,7 @@ content:
 tags: balancing-rule balancing rules api load-balancer
 dates:
   posted: 2023-11-27
-  validation: 2024-06-18
+  validation: 2024-12-23
 categories:
   - network
 ---

@@ -7,7 +7,7 @@ content:
   paragraph: Learn how to set up frontends and backends with Scaleway Load Balancer. Step-by-step guide for configuring efficient network routing and load distribution.
 tags: load-balancer load balancer
 dates:
-  validation: 2024-06-18
+  validation: 2024-12-23
   posted: 2021-05-26
 categories:
   - network

@@ -6,11 +6,11 @@ content:
   h1: Configuring your Load Balancer's frontend
   paragraph: Discover essential tips for configuring frontends with Scaleway Load Balancer. Optimize your network setup with detailed, easy-to-follow instructions.
 tags: load-balancer
-categories: 
+categories:
   - load-balancer
   - network
 dates:
-  validation: 2024-06-18
+  validation: 2024-12-23
   posted: 2023-06-05
 ---
 

@@ -6,11 +6,11 @@ content:
   h1: Configuring health checks
   paragraph: Learn how to configure effective health checks for your services with Scaleway Load Balancer. Ensure optimal performance and reliability with expert guidance.
 tags: load-balancer health-check health interval transient-state unhealthy-threshold
-categories: 
+categories:
   - load-balancer
   - network
 dates:
-  validation: 2024-06-18
+  validation: 2024-12-23
   posted: 2023-06-05
 ---
 
@@ -22,7 +22,7 @@ In this document, we explain some of the different settings available when setti
 
 ## Health check types
 
-Health checks are available in many different types. By default, the health check type is set to be the same as that of the [backend protocol](/network/load-balancer/reference-content/configuring-backends/#protocol-and-port), that is to say **TCP** or **HTTP**. However, this can be overridden. 
+Health checks are available in many different types. By default, the health check type is set to be the same as that of the [backend protocol](/network/load-balancer/reference-content/configuring-backends/#protocol-and-port), that is to say **TCP** or **HTTP**. However, this can be overridden.
 
 The following health check types are available:
 
@@ -33,7 +33,7 @@ When selecting HTTP health checks, you are prompted to select values for the fol
 **Method**: Specifies the HTTP method the Load Balancer uses to send health check requests to the backend server. The following options are available:
 
 - `GET`: The Load Balancer sends a simple request to retrieve information. This is the most common choice for a health check method.
-- `POST`: The Load Balancer submits data for processing to a specified resource endpoint. 
+- `POST`: The Load Balancer submits data for processing to a specified resource endpoint.
 - `PUT`: The Load Balancer submits data to update a specified resource.
 
 While `GET` is a commonly-used method as it is considered a "safe" choice with minimal side effects on the backend server, `POST` or `PUT` may be suitable for checking the health of applications running on backend servers that rely heavily on form submissions, data updates or write operations.
@@ -49,7 +49,7 @@ While `GET` is a commonly-used method as it is considered a "safe" choice with m
 For MYSQL health checks, you are prompted to select the database username. The MYSQL health check sends two MySQL packets to the server: first a Client Authentication packet and then a QUIT packet to properly close the MySQL session. The received MySQL Handshake Initialization packet (and/or Error packet) is then parsed. This basic but useful test does not produce errors or aborted connections on the server. However, bear in mind that it does not check database presence or database consistency (an external check e.g. with xinetd would be required for this).
     <Message type="tip">
       The user specified for the health check must be unlocked and authorized without a password.
-      
+
       For MySQL versions < 8.0:
 
       ```
@@ -59,14 +59,14 @@ For MYSQL health checks, you are prompted to select the database username. The M
       For MySQL versions >= 8.0 and < 9.0, the `mysql_native_password` authentication plugin is no longer enabled by default. Therefore you need to activate it with the following setting:
 
       ```
-      mysql_native_password=ON 
+      mysql_native_password=ON
       ```
 
       You can then create the user:
 
       ```
       CREATE USER '<USERNAME>'@'<IP_ADDRESS_LB>' IDENTIFIED WITH mysql_native_password;
-      ```     
+      ```
     </Message>
 
     <Message type="important">
@@ -90,7 +90,7 @@ No additional settings are required for REDIS health checks. A PING redis comman
 
 ### TCP
 
-No additional settings are required for TCP health checks. This check consists of a connection attempt that either fails or succeeds. 
+No additional settings are required for TCP health checks. This check consists of a connection attempt that either fails or succeeds.
 
 ## TLS
 
@@ -100,7 +100,7 @@ The activation setting is inherited from your [backend configuration](/network/l
 
 ## Verify certificate
 
-If you activated TLS encryption for your health check, the Verify Certificate setting displays. This determines whether the backend server's certificate is verified during health checks. 
+If you activated TLS encryption for your health check, the Verify Certificate setting displays. This determines whether the backend server's certificate is verified during health checks.
 
 This setting is inherited from the [backend configuration](/network/load-balancer/reference-content/configuring-backends/#verify-certificate) and cannot be overridden:
 - If you activated TLS on your backend, the Verify Certificate setting you chose there is inherited for health checks.
@@ -110,7 +110,7 @@ The above also applies if you edit your backend settings after creating the back
 
 ## Proxy Protocol
 
-Proxy Protocol enables the original client IP address to be passed to the backend server in a standardized way during health checks. Note that the backend server must support the selected Proxy Protocol. 
+Proxy Protocol enables the original client IP address to be passed to the backend server in a standardized way during health checks. Note that the backend server must support the selected Proxy Protocol.
 
 The following versions of Proxy Protocol are available:
 
@@ -134,5 +134,5 @@ Recommended settings for all the parameters below are selected by default, howev
 * **Unhealthy threshold:** The number of consecutive failed health checks after which a backend server is diagnosed as unhealthy, and its status is changed to `Down`. Requests/connections will no longer be forwarded to servers with a `down` status.The default value is 3, the minimum value is 1 and the maximum value is 9 999.
 * **Interval (transient state)**: The interval between two consecutive health checks when a server is in a transient state. The default value is 0.5, the minimum value is 0.1 and the maximum value is 2 147 483. Note that a backend server is in a transient state when:
     * It is considered `up`, but then fails a health check. It stays in this transient state until the number of consecutive unsuccessful health checks goes above the unhealthy threshold, at which point it switches to `down`.
-    * It is considered `down`, but then passes a health check. It stays in this transient state until the number of consecutive successful health checks goes above two, at which point it switches to `up`. 
+    * It is considered `down`, but then passes a health check. It stays in this transient state until the number of consecutive successful health checks goes above two, at which point it switches to `up`.
 * **Shut down sessions if unhealthy**: Activate this option if you want the Load Balancer to shut down any open sessions to a given backend server as soon as that server is diagnosed as unhealthy.