-
Notifications
You must be signed in to change notification settings - Fork 243
[K8S] Documentation Kubernetes node images #2629
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
5359262
feat(k8s): kubernetes node images
bene2k1 6dda6fc
feat(k8s): node images
bene2k1 5006212
feat(k8s): node images
bene2k1 e213eeb
Apply suggestions from code review
bene2k1 be41922
Apply suggestions from code review
bene2k1 dc2c426
feat(k8s): upgrade node pools
bene2k1 f2356ae
feat(k8s): node images
bene2k1 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
55 changes: 55 additions & 0 deletions
55
containers/kubernetes/how-to/upgrade-cluster-node-image.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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. | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
<Navigation title="See Also"> | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
<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> |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
52 changes: 52 additions & 0 deletions
52
containers/kubernetes/reference-content/kubernetes-node-images.mdx
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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? | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
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. | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
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 | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- Faster provisioning of new nodes | ||
- No more need for cluster reboots | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- 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 | ||
bene2k1 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
- 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.