scaleway · bene2k1 · Jan 18, 2024 · Jan 18, 2024 · Jan 18, 2024 · Jan 24, 2024
@@ -24,6 +24,4 @@ categories:
 1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Kubernetes Kapsule overview displays.
 2. Click the name of the cluster you want to access. The cluster overview page displays. This page provides several pieces of information about your cluster:
 3. Click **Dashboard**. You are taken to your cluster's Kubernetes dashboard.
-   Here, you can troubleshoot your containerized application, manage the cluster resources, get an overview of applications running on your cluster, and create or modify certain resources.
-
-
+   Here, you can troubleshoot your containerized application, manage the cluster resources, get an overview of applications running on your cluster, and create or modify certain resources.
@@ -0,0 +1,55 @@
+---
+meta:
+  title: How to upgrade your cluster node images
+  description: This page explains how to upgrade your node images.
+content:
+  h1: How to upgrade your cluster node images
+  paragraph: This page explains how to upgrade your node images.
+tags: kubernetes kubernetes-kapsule kapsule node image upgrade
+dates:
+  validation: 2024-01-18
+  posted: 2024-01-18
+categories:
+  - kubernetes
+---
+
+Kubernetes Kapsule clusters benefit from regular updates to their [node images](/containers/kubernetes/reference-content/kubernetes-node-images/). To profit of the latest features, it is important to stay up-to-date by upgrading these images. 
+This guide outlines the process for upgrading node images in your Kubernetes Kapsule cluster and provides instructions on updating node pool images without changing the Kubernetes version.
+
+<Message type="tip">
+  If you wish to upgrade the Kubernetes version of your cluster, refer to the documentation on [Upgrading a Kubernetes Cluster](/containers/kubernetes/how-to/upgrade-kubernets-version/).
+</Message>
+
+<Message type="requirement">
+  - You have an account and are logged into the [Scaleway console](https://console.scaleway.com)
+  - You have [created](/containers/kubernetes/how-to/create-cluster) a Kubernetes Kapsule cluster
+</Message>
+
+## Node Image Upgrade Process
+
+### Automatic Upgrade for Kubernetes 1.30 or later
+
+For Kubernetes clusters running version `>=1.30`, the new node image is applied automatically to all clusters created using this version. To upgrade the version of your node image, follow these steps:
+
+1. Click **Kubernetes** under **Containers** on the side menu. A list of your Kubernetes Kapsule clusters displays.
+2. Click the cluster name you wish to upgrade the pool. The cluster information page displays.
+3. Navigate to the cluster's configuration settings and select the option to upgrade node pools. This process will automatically apply the latest node image to your cluster.
+
+### Hybrid Roll-out Strategy for Kubernetes 1.29 or earlier
+
+For Kubernetes clusters running version `<=1.29`, a hybrid roll-out strategy is implemented. Follow these steps to upgrade node images in such clusters:
+
+* **Automatic deployment for new nodes:**
+   - Any newly created node is automatically deployed using the new image system.
+   - Nodes created through auto-scaling are also deployed using the new system.
+* **Transition for replaced nodes:**
+   - Replaced nodes transition to the new image system as part of the upgrade process.
+* **New node pool deployment:**
+   - Any new node pool is deployed using the new node image.
+* **Legacy nodes maintenance:**
+   - Legacy nodes, including upgraded nodes, maintain the older system for retro compatibility.
+
+<Navigation title="See Also">
+  <PreviousButton to="/containers/kubernetes/how-to/access-kubernetes-dashboard/">How to access the dashboard of a Kubernetes Kapsule cluster</PreviousButton>
+  <NextButton to="/containers/kubernetes/how-to/upgrade-kubernetes-version/">How to upgrade the Kubernetes version on a Kapsule cluster</NextButton>
+</Navigation>
@@ -143,4 +143,3 @@ scw k8s pool create zone=$OLD_POOL_ZONE size=$SIZE_OF_YOUR_OLD_POOL version=$NEW
 
 The process is quite similar to the previous one except you need to repeat the steps for each minor version.
 
-
@@ -0,0 +1,52 @@
+---
+meta:
+  title: Kubernetes node images
+  description: This page provides information about Kubernetes node images for your Kubernetes cluster
+content:
+  h1: Kubernetes node images
+  paragraph: This page provides information about Kubernetes node images for your Kubernetes cluster
+tags: kubernetes load-balancer loadbalancer service annotations ip expose
+dates:
+  validation: 2024-01-18
+  posted: 2024-01-18
+categories:
+  - kubernetes
+---
+
+Kubernetes node images refer to the containerized operating system and runtime environment that run on each node within a Kubernetes cluster.
+These images encapsulate the essential components necessary for hosting and managing containers, such as the container runtime (e.g. `containerd`), the kubelet (Kubernetes agent), and other dependencies.
+
+In Kubernetes, a node is a physical or virtual machine inside a cluster, that serves for deploying and running containerized workloads.
+A Kubernetes cluster consists of a main node (control plane) and multiple worker nodes. These worker nodes are where the actual containers run.
+
+## What does Scaleways node images contain?
+
+Scaleway Kubernetes node images are customized Ubuntu Linux-based OS images, specifically built for Scaleway's Kubernetes infrastructure.
+These images include `containerd`, a high-performance container runtime, and Scaleway's Kubernetes Kapsule agent, facilitating communication between the Kubernetes control plane and the underlying infrastructure.
+
+## What are the benefits of the new node image system?
+
+The new node images offers advantages in cluster consistency, management ease, and security. 
+Our images are optimized for performance and compatibility with the Kubernetes control plane and integrate seamlessly with the Kubernetes ecosystem.
+
+The main benefits of using the new node images are:
+- Accelerated upgrade timelines
+    - Uninterrupted service continuity with hot upgrades
+    - Increased upgrade frequency for large clusters
+- Faster provisioning of new nodes
+- No more need for cluster reboots
+- Expanded possibilities for incorporating new features
+
+## With which versions of Kubernetes are the new node images compatible?
+
+If your Kubernetes cluster runs version `<=1.29` we have implemented a hybrid roll-out strategy:
+
+-  Any newly created node is deployed using the new image system.
+    - Replaced nodes transition to the new image system.
+    - Any new node pool is deployed using the new node image
+    - Nodes created through auto-scaling are deployed using the new system
+- Legacy nodes maintain the older system for retro compatibility
+    - Upgraded nodes follow the same approach, retaining the older system
+
+If your cluster is running Kubernetes `=>1.30` it will use the new compute image
+    - Pool upgrades bring compute images to its nodes
diff --git a/menu/navigation.json b/menu/navigation.json
@@ -1376,6 +1376,10 @@
                     "label": "Access the Kubernetes dashboard",
                     "slug": "access-kubernetes-dashboard"
                   },
+                  {
+                    "label": "Upgrade your cluster node images",
+                    "slug": "upgrade-cluster-node-image"
+                  },
                   {
                     "label": "Upgrade the Kubernetes version on a Kapsule cluster",
                     "slug": "upgrade-kubernetes-version"
@@ -1476,6 +1480,10 @@
                     "label": "Creating and configuring a Load Balancer service",
                     "slug": "kubernetes-load-balancer"
                   },
+                  {
+                    "label": "Understanding Kubernetes node images",
+                    "slug": "kubernetes-node-images"
+                  },
                   {
                     "label": "Using a Load Balancer with Ingress",
                     "slug": "lb-ingress-controller"
Original file line number	Diff line number	Diff line change
Expand Up		@@ -143,4 +143,3 @@ scw k8s pool create zone=$OLD_POOL_ZONE size=$SIZE_OF_YOUR_OLD_POOL version=$NEW

		The process is quite similar to the previous one except you need to repeat the steps for each minor version.