docs(k8s): review docs and tutorials 2024-11-04 (#3932)

containers/kubernetes/reference-content/kubernetes-load-balancer.mdx

@@ -7,13 +7,13 @@ content:
   paragraph: This page provides information about creating and configuring a Load Balancer service for your Kubernetes cluster
 tags: kubernetes load-balancer loadbalancer service annotations ip expose
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2023-10-25
 categories:
   - kubernetes
 ---
 
-Creating a Load Balancer for your Kubernetes cluster allows you to expose an application running inside your cluster to the internet.
+Creating a [Load Balancer](/containers/kubernetes/concepts/#load-balancer) for your Kubernetes cluster allows you to expose an application running inside your cluster to the internet.
 
 In this document, we summarize when to create a Load Balancer for your cluster (as opposed to a different solution for exposing your application), and take you through the basic steps to create and configure your Load Balancer.
 
@@ -34,7 +34,7 @@ On the other hand, if you have multiple services running in a more complex clust
 
 Read the [full documentation](/containers/kubernetes/reference-content/exposing-services/) on different ways to expose your services for full details, and links to the relevant documentation for each possibility.
 
-## Creating a Load Balancer for your cluster: overview
+## Creating a Load Balancer for your cluster: Overview
 
 Here is a quick overview of how to create a Load Balancer for your cluster:
 
@@ -48,7 +48,7 @@ Here is a quick overview of how to create a Load Balancer for your cluster:
 Load Balancers for Kubernetes clusters should **always** be provisioned via the cluster's Cloud Controller Manager. It is **not** correct procedure to provision the Load Balancer by creating a Scaleway Load Balancer in the console or via the API, and then attempting to use it as your cluster's external Load Balancer. Similarly, you cannot use the Scaleway console or devtools to edit your cluster's Load Balancer after creation, this must be done via the CCM, as detailed in this documentation.
 </Message>
 
-## Creating a Load Balancer for your cluster: step by step
+## Creating a Load Balancer for your cluster: Step by step
 
 <Macro id="requirements" />
 

containers/kubernetes/reference-content/managing-load-balancer-ips.mdx

@@ -7,17 +7,17 @@ content:
   paragraph: Managing Load Balancer IPs
 tags: load-balancer load-balancer-ip kubernetes ip flexible-ip
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2021-08-12
 categories:
   - kubernetes
 ---
 
-By default, when you create a Load Balancer for your cluster, it will be assigned a random public IP address. When you delete the Load Balancer, the IP address will also be deleted and cannot be retrieved to transfer to another Load Balancer service in your cluster.
+By default, when you create a [Load Balancer](/containers/kubernetes/concepts/#load-balancer) for your cluster, it will be assigned a random public IP address. When you delete the Load Balancer, the IP address will also be deleted and cannot be retrieved to transfer to another Load Balancer service in your cluster.
 
 However, it is possible to use [flexible IP addresses](/network/load-balancer/concepts/#flexible-ip-address) with your cluster's Load Balancer, to give you more control over the IPs being used. Flexible IP addresses can be kept in your account even if/when their associated Load Balancer is deleted. They can then be assigned to a new Load Balancer in the future.
 
-You can view your existing Load Balancer flexible IP addresses, and create new ones, in the [Scaleway console](https://console.scaleway.com/load-balancer/ips). Alternatively, use the [API](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-ip-addresses-list-ip-addresses) or other devtools.
+You can view your existing Load Balancer flexible IP addresses, and create new ones, in the [Scaleway console](https://console.scaleway.com/load-balancer/ips). Alternatively, use the [API](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-ip-addresses-list-ip-addresses) or other development tools.
 
 <Message type="note">
 Load Balancer flexible IPs have the following limitations:

containers/kubernetes/reference-content/multi-az-clusters.mdx

@@ -7,13 +7,13 @@ content:
   paragraph: This page explains how to ensure resiliency with multi-AZ Kubernetes clusters
 tags: kubernetes persistent volume persistent-volume
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2023-10-17
 categories:
   - kubernetes
 ---
 
-Kubernetes Kapsule clusters can use Private Networks, providing a default security layer for worker nodes. Furthermore, these clusters can deploy node pools across various Availability Zones (AZs).
+Kubernetes Kapsule clusters can use [Private Networks](/faq/private-networks/#what-are-private-networks), providing a default security layer for worker nodes. Furthermore, these clusters can deploy node pools across various [Availability Zones (AZs)](/containers/kubernetes/concepts/#multi-az-clusters).
 
 <Lightbox src="scaleway-k8s-multi-az-cluster.webp" size="large" />
 
@@ -42,8 +42,8 @@ For more information, refer to the [official Kubernetes best practices for runni
 
 - Kapsule's Control Plane network access is managed by a Load Balancer in the primary zone of each region. If this zone fails globally, the Control Plane will be unreachable, even if the cluster spans multiple zones. This limitation also applies to HA Dedicated Control Planes.
 - Persistent volumes are limited to their Availability Zone (AZ). Applications must replicate data across persistent volumes in different AZs to maintain high availability in case of zone failures.
-- In "controlled isolation" mode, nodes access the Control Plane via their public IPs. If two AZs can't communicate (split-brain scenario), nodes won't appear unhealthy from Kubernetes' perspective, but communication between nodes in different AZs will be disrupted. Applications must handle this scenario if they use components across multiple AZs.
-- In "full isolation" mode, nodes also use the Public Gateway to access the Control Plane. If nodes can't reach the Public Gateway (e.g. because of Private Network failure in an AZ), they will become unhealthy. As there is only one Public Gateway per Private Network, losing the AZ with the Public Gateway results in the loss of all nodes in all private pools across all AZs.
+- In "controlled isolation" mode, nodes access the Control Plane via their public IPs. If two AZs can not communicate (split-brain scenario), nodes will not appear unhealthy from Kubernetes' perspective, but communication between nodes in different AZs will be disrupted. Applications must handle this scenario if they use components across multiple AZs.
+- In "full isolation" mode, nodes also use the Public Gateway to access the Control Plane. If nodes cannot reach the Public Gateway (e.g. because of Private Network failure in an AZ), they will become unhealthy. As there is only one Public Gateway per Private Network, losing the AZ with the Public Gateway results in the loss of all nodes in all private pools across all AZs.
 
 <Message type="note">
 It is important to note that the scalability and reliability of Kubernetes does not automatically ensure the scalability and reliability of an application hosted on it. While Kubernetes is a robust and scalable platform, each application must independently implement measures to achieve scalability and reliability, ensuring it avoids bottlenecks and single points of failure. Therefore, although Kubernetes itself remains responsive, the responsiveness of your application relies on your design and deployment choices.
@@ -57,7 +57,7 @@ It is important to note that the scalability and reliability of Kubernetes does
 
 ### Prerequisites for setting up a multi-AZ cluster
 
-- Your cluster must be compatible with, and connected to a Private Network. If it's not, you will need to migrate your cluster following the [procedure through the console, API, or Terraform](/containers/kubernetes/reference-content/secure-cluster-with-private-network/).
+- Your cluster must be compatible with, and connected to a Private Network. If it is not, you will need to migrate your cluster following the [procedure through the console, API, or Terraform](/containers/kubernetes/reference-content/secure-cluster-with-private-network/).
 
 - Ensure the node types required for your pool are available in your chosen AZs, as not all node types are available in every AZ and stocks might be limited.
 

containers/kubernetes/reference-content/wildcard-dns.mdx

@@ -7,7 +7,7 @@ content:
   paragraph: This page explains how to route external traffic in Kubernetes using wildcard DNS and ingress controller
 tags: kubernetes load-balancer-service wildcard ingress
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2021-08-12
 categories:
   - kubernetes

tutorials/configure-plex-s3/index.mdx

@@ -1,17 +1,17 @@
 ---
 meta:
-  title: Configuring Plex Media Server with Object Storage
-  description: This page shows how to set up a media server with Plex and Object Storage
+  title: Configuring Plex Media Server with Scaleway Object Storage
+  description: This page shows how to set up a media server with Plex and Scaleway Object Storage
 content:
-  h1: Configuring Plex Media Server with Object Storage
-  paragraph: This page shows how to configure Plex media server with Object Storage
+  h1: Configuring Plex Media Server with Scaleway Object Storage
+  paragraph: This page shows how to configure Plex media server with Scaleway Object Storage
 tags: Plex-Media-Server streaming s3fs lucidlink
 hero: assets/scaleway-configuring-plex-s3.webp
 categories:
   - object-storage
   - instances
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2018-09-24
 ---
 

tutorials/deploy-k3s-cluster-with-cilium/index.mdx

@@ -10,7 +10,7 @@ hero:
 categories:
   - kubernetes
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2023-10-23
 ---
 

tutorials/store-s3-transmit/index.mdx

@@ -1,22 +1,23 @@
 ---
 meta:
-  title: Storing objects with Object Storage and Transmit 5
-  description: This page shows you how to store objects with Transmit 5.
+  title: Storing objects with Scaleway Object Storage and Transmit 5
+  description: This page shows you how to store objects with Transmit 5 on Scaleway's Object Storage platform.
 content:
-  h1: Storing objects with Object Storage and Transmit 5
-  paragraph: This page shows you how to store objects with Transmit 5.
+  h1: Storing objects with Scalewy Object Storage and Transmit 5
+  paragraph: This page shows you how to store objects with Transmit 5 on Scaleway's Object Storage platform.
 tags: object-storage Transmit-5
 categories:
   - object-storage
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2018-06-04
 ---
 
-Object Storage allows you to store any kind of object (documents, images, videos, etc.) and retrieve them at a later time from anywhere.
+Scaleway Object Storage provides a scalable and accessible solution for storing and retrieving various types of objects, including documents, images, videos, and more, from anywhere in the world.
+
+With Scaleway Object Storage, you can easily store and serve files, such as images, over HTTPS.
+Additionally, you can manage your storage using the intuitive control panel or use a range of available tools to interact with your Object Storage buckets, streamlining your workflow and enhancing productivity.
 
-For instance, you can store images and they will be accessible using HTTPS.
-You can use the control panel to manage your storage. Some tools exist to interact with Object Storage.
 
 <Macro id="requirements" />
 
@@ -28,14 +29,14 @@ You can use the control panel to manage your storage. Some tools exist to intera
 
 To access Object Storage using s3md, you need to [configure your API key](/identity-and-access-management/iam/how-to/create-api-keys/).
 
-## Downloading Transmit
+## Downloading Transmit 5
 
-Transmit is a powerful and easy-to-use solution to manage Object Storage from your Mac.
-It provides a clean and straightforward interface to create, list, and delete buckets, and download, upload, and delete objects inside the Object Storage.
+Transmit 5 is a powerful and easy-to-use solution to manage Object Storage from your Mac.
+It provides a clean and straightforward interface to create, list, and delete buckets, and download, upload, and delete objects inside the Object Storage bucket.
 
 [Download Transmit 5](https://panic.com/transmit/).
 
-## Configuring Transmit
+## Configuring Transmit 5
 
 1. Open the application. On the right-hand side, you see the remote server list.
 2. Click `+` to create a new server profile.

tutorials/vuls-security-scanner/index.mdx

@@ -9,7 +9,7 @@ categories:
   - instances
 tags: compute Vuls security NVD OVAL
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-09
   posted: 2019-03-19
 ---
 

tutorials/wordpress-lemp-stack/index.mdx

@@ -10,7 +10,7 @@ hero: assets/scaleway_wordpress_lemp.webp
 categories:
   - instances
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2018-11-09
 ---
 

tutorials/zabbix-monitoring/index.mdx

@@ -9,7 +9,7 @@ tags: instances Zabbix monitoring MariaDB
 categories:
   - instances
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2019-06-17
 ---
 

tutorials/zulip/index.mdx

@@ -10,7 +10,7 @@ hero: assets/scaleway_zulip.webp
 categories:
   - instances
 dates:
-  validation: 2024-04-29
+  validation: 2024-11-04
   posted: 2021-10-21
 ---