Skip to content

Commit

Permalink
Bump Kubernetes to v1.26.9
Browse files Browse the repository at this point in the history
  • Loading branch information
twz123 committed Sep 14, 2023
1 parent 5cd4a6e commit 412bee1
Show file tree
Hide file tree
Showing 25 changed files with 161 additions and 161 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/publish-docs-manual.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ on:
workflow_dispatch:
inputs:
version:
description: 'Version tag (e.g."v1.26.8+k0s.0")'
description: 'Version tag (e.g."v1.26.9+k0s.0")'
required: true

env:
Expand Down
2 changes: 1 addition & 1 deletion docs/airgap-install.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ metadata:
name: k0s-cluster
spec:
k0s:
version: 1.26.8+k0s.0
version: 1.26.9+k0s.0
hosts:
- role: controller
ssh:
Expand Down
8 changes: 4 additions & 4 deletions docs/autopilot-multicommand.md
Original file line number Diff line number Diff line change
Expand Up @@ -62,20 +62,20 @@ processed by **autopilot**.
6: spec:
7: commands:
8: - airgapupdate:
9: version: v1.26.8+k0s.0
9: version: v1.26.9+k0s.0
10: platforms:
11: linux-amd64:
12: url: https://github.com/k0sproject/k0s/releases/download/v1.26.8+k0s.0/k0s-airgap-bundle-v1.26.8+k0s.0-amd64
12: url: https://github.com/k0sproject/k0s/releases/download/v1.26.9+k0s.0/k0s-airgap-bundle-v1.26.9+k0s.0-amd64
13: workers:
14: discovery:
15: static:
16: nodes:
17: - worker0
18: - k0supdate:
19: version: v1.26.8+k0s.0
19: version: v1.26.9+k0s.0
20: platforms:
21: linux-amd64:
22: url: https://github.com/k0sproject/k0s/releases/download/v1.26.8+k0s.0/k0s-v1.26.8+k0s.0-amd64
22: url: https://github.com/k0sproject/k0s/releases/download/v1.26.9+k0s.0/k0s-v1.26.9+k0s.0-amd64
23: targets:
24: controllers:
25: discovery:
Expand Down
4 changes: 2 additions & 2 deletions docs/autopilot.md
Original file line number Diff line number Diff line change
Expand Up @@ -96,10 +96,10 @@ spec:
commands:
- k0supdate:
version: v1.26.8+k0s.0
version: v1.26.9+k0s.0
platforms:
linux-amd64:
url: https://github.com/k0sproject/k0s/releases/download/v1.26.8+k0s.0/k0s-v1.26.8+k0s.0-amd64
url: https://github.com/k0sproject/k0s/releases/download/v1.26.9+k0s.0/k0s-v1.26.9+k0s.0-amd64
sha256: '0000000000000000000000000000000000000000000000000000000000000000'
targets:
controllers:
Expand Down
2 changes: 1 addition & 1 deletion docs/configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -76,7 +76,7 @@ spec:
version: 0.0.33-k0s
kubeproxy:
image: registry.k8s.io/kube-proxy
version: v1.26.8
version: v1.26.9
kuberouter:
cni:
image: docker.io/cloudnativelabs/kube-router
Expand Down
16 changes: 8 additions & 8 deletions docs/docker-shim.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,8 +32,8 @@ Get a list of all nodes (k0s is still version 1.23, which already includes the d
sudo k0s kubectl get nodes -o wide

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 52m v1.26.8+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready <none> 12s v1.26.8+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 52m v1.26.9+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready <none> 12s v1.26.9+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
```

cordon and drain the nodes (migrate one by one):
Expand All @@ -47,8 +47,8 @@ sudo k0s kubectl drain ip-10-0-62-250.eu-west-1.compute.internal --ignore-daemon
sudo k0s kubectl get nodes -o wide

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 56m v1.26.8+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready,SchedulingDisabled <none> 3m40s v1.26.8+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 56m v1.26.9+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready,SchedulingDisabled <none> 3m40s v1.26.9+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
```

Stop k0s on the node:
Expand Down Expand Up @@ -143,8 +143,8 @@ On the controller, you'll be able to see the worker started with the new docker
sudo k0s kubectl get nodes -o wide

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 117m v1.26.8+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready,SchedulingDisabled <none> 64m v1.26.8+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 117m v1.26.9+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready,SchedulingDisabled <none> 64m v1.26.9+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
```

### Uncordon the Node
Expand All @@ -161,6 +161,6 @@ You should now see the node Ready for scheduling with the docker Runtime:
sudo k0s kubectl get nodes -o wide

NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 119m v1.26.8+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready <none> 66m v1.26.8+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
ip-10-0-49-188.eu-west-1.compute.internal Ready control-plane 119m v1.26.9+k0s 10.0.49.188 <none> Ubuntu 20.04.4 LTS 5.13.0-1022-aws docker://20.10.16
ip-10-0-62-250.eu-west-1.compute.internal Ready <none> 66m v1.26.9+k0s 10.0.62.250 <none> Ubuntu 20.04.4 LTS 5.13.0-1017-aws docker://20.10.16
```
4 changes: 2 additions & 2 deletions docs/install.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,7 @@ Though the Quick Start material is written for Debian/Ubuntu, you can use it for
```shell
$ sudo k0s status
Version: v1.26.8+k0s.0
Version: v1.26.9+k0s.0
Process ID: 436
Role: controller
Workloads: true
Expand All @@ -77,7 +77,7 @@ Though the Quick Start material is written for Debian/Ubuntu, you can use it for
```shell
$ sudo k0s kubectl get nodes
NAME STATUS ROLES AGE VERSION
k0s Ready <none> 4m6s v1.26.8+k0s
k0s Ready <none> 4m6s v1.26.9+k0s
```
## Uninstall k0s
Expand Down
6 changes: 3 additions & 3 deletions docs/k0s-in-docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ You will require a [Docker environment](https://docs.docker.com/get-docker/) run

The k0s containers are published both on Docker Hub and GitHub. For reasons of simplicity, the examples given here use Docker Hub (GitHub requires a separate authentication that is not covered). Alternative links include:

- docker.io/k0sproject/k0s:v1.26.8-k0s.0
- ghcr.io/k0sproject/k0s:v1.26.8-k0s.0
- docker.io/k0sproject/k0s:v1.26.9-k0s.0
- ghcr.io/k0sproject/k0s:v1.26.9-k0s.0

**Note:** Due to Docker Hub tag validation scheme, we have to use `-` as the k0s version separator instead of the usual `+`. So for example k0s version `v1.26.8+k0s.0` is tagged as `docker.io/k0sproject/k0s:v1.26.8-k0s.0`.
**Note:** Due to Docker Hub tag validation scheme, we have to use `-` as the k0s version separator instead of the usual `+`. So for example k0s version `v1.26.9+k0s.0` is tagged as `docker.io/k0sproject/k0s:v1.26.9-k0s.0`.

## Start k0s

Expand Down
8 changes: 4 additions & 4 deletions docs/k0s-multi-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,13 +24,13 @@ The download script accepts the following environment variables:

| Variable | Purpose |
|:----------------------------|:--------------------------------------------------|
| `K0S_VERSION=v1.26.8+k0s.0` | Select the version of k0s to be installed |
| `K0S_VERSION=v1.26.9+k0s.0` | Select the version of k0s to be installed |
| `DEBUG=true` | Output commands and their arguments at execution. |

**Note**: If you require environment variables and use sudo, you can do:

```shell
curl -sSLf https://get.k0s.sh | sudo K0S_VERSION=v1.26.8+k0s.0 sh
curl -sSLf https://get.k0s.sh | sudo K0S_VERSION=v1.26.9+k0s.0 sh
```

### 2. Bootstrap a controller node
Expand Down Expand Up @@ -126,7 +126,7 @@ To get general information about your k0s instance's status:
```

```shell
Version: v1.26.8+k0s.0
Version: v1.26.9+k0s.0
Process ID: 2769
Parent Process ID: 1
Role: controller
Expand All @@ -144,7 +144,7 @@ sudo k0s kubectl get nodes

```shell
NAME STATUS ROLES AGE VERSION
k0s Ready <none> 4m6s v1.26.8+k0s
k0s Ready <none> 4m6s v1.26.9+k0s
```

You can also access your cluster easily with [Lens](https://k8slens.dev/), simply by copying the kubeconfig and pasting it to Lens:
Expand Down
22 changes: 11 additions & 11 deletions docs/nllb.md
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ metadata:
name: k0s-cluster
spec:
k0s:
version: v1.26.8+k0s.0
version: v1.26.9+k0s.0
config:
spec:
network:
Expand Down Expand Up @@ -176,11 +176,11 @@ level=info msg="==> Running phase: Validate hosts"
level=info msg="==> Running phase: Gather k0s facts"
level=info msg="==> Running phase: Validate facts"
level=info msg="==> Running phase: Upload k0s binaries to hosts"
level=info msg="[ssh] 10.81.146.254:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.8+k0s.0"
level=info msg="[ssh] 10.81.146.113:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.8+k0s.0"
level=info msg="[ssh] 10.81.146.51:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.8+k0s.0"
level=info msg="[ssh] 10.81.146.198:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.8+k0s.0"
level=info msg="[ssh] 10.81.146.184:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.8+k0s.0"
level=info msg="[ssh] 10.81.146.254:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.9+k0s.0"
level=info msg="[ssh] 10.81.146.113:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.9+k0s.0"
level=info msg="[ssh] 10.81.146.51:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.9+k0s.0"
level=info msg="[ssh] 10.81.146.198:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.9+k0s.0"
level=info msg="[ssh] 10.81.146.184:22: uploading k0s binary from /home/k0sctl/.cache/k0sctl/k0s/linux/amd64/k0s-v1.26.9+k0s.0"
level=info msg="==> Running phase: Configure k0s"
level=info msg="[ssh] 10.81.146.254:22: validating configuration"
level=info msg="[ssh] 10.81.146.184:22: validating configuration"
Expand Down Expand Up @@ -220,7 +220,7 @@ level=info msg="[ssh] 10.81.146.51:22: waiting for node to become ready"
level=info msg="==> Running phase: Release exclusive host lock"
level=info msg="==> Running phase: Disconnect from hosts"
level=info msg="==> Finished in 3m30s"
level=info msg="k0s cluster version v1.26.8+k0s.0 is now installed"
level=info msg="k0s cluster version v1.26.9+k0s.0 is now installed"
level=info msg="Tip: To access the cluster you can now fetch the admin kubeconfig using:"
level=info msg=" k0sctl kubeconfig"
```
Expand Down Expand Up @@ -258,8 +258,8 @@ listed, too:
```console
$ kubectl get nodes -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k0s-worker-0 Ready <none> 2m16s v1.26.8+k0s 10.81.146.198 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-1 Ready <none> 2m15s v1.26.8+k0s 10.81.146.51 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-0 Ready <none> 2m16s v1.26.9+k0s 10.81.146.198 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-1 Ready <none> 2m15s v1.26.9+k0s 10.81.146.51 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
```

There is one node-local load balancer pod running for each worker node:
Expand Down Expand Up @@ -304,8 +304,8 @@ $ sed -i s#https://10\\.81\\.146\\.254:6443#https://10.81.146.184:6443#g k0s-kub
$ kubectl get nodes -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
k0s-worker-0 Ready <none> 3m35s v1.26.8+k0s 10.81.146.198 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-1 Ready <none> 3m34s v1.26.8+k0s 10.81.146.51 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-0 Ready <none> 3m35s v1.26.9+k0s 10.81.146.198 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
k0s-worker-1 Ready <none> 3m34s v1.26.9+k0s 10.81.146.51 <none> Alpine Linux v3.17 5.15.83-0-virt containerd://1.6.18
$ kubectl -n kube-system get pods -owide -l app.kubernetes.io/managed-by=k0s,app.kubernetes.io/component=nllb
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
Expand Down
10 changes: 5 additions & 5 deletions docs/raspberry-pi4.md
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ Download a [k0s release](https://github.com/k0sproject/k0s/releases/latest). For
example:

```shell
wget -O /tmp/k0s https://github.com/k0sproject/k0s/releases/download/v1.26.8+k0s.0/k0s-v1.26.8+k0s.0-arm64 # replace version number!
wget -O /tmp/k0s https://github.com/k0sproject/k0s/releases/download/v1.26.9+k0s.0/k0s-v1.26.9+k0s.0-arm64 # replace version number!
sudo install /tmp/k0s /usr/local/bin/k0s
```

Expand All @@ -142,7 +142,7 @@ At this point you can run `k0s`:

```console
ubuntu@ubuntu:~$ k0s version
v1.26.8+k0s.0
v1.26.9+k0s.0
```

To check if k0s's [system requirements](system-requirements.md) and [external
Expand Down Expand Up @@ -288,7 +288,7 @@ When the cluster is up, try to have a look:
```console
ubuntu@ubuntu:~$ sudo k0s kc get nodes -owide
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
ubuntu Ready control-plane 4m41s v1.26.8+k0s 10.152.56.54 <none> Ubuntu 22.04.1 LTS 5.15.0-1013-raspi containerd://1.6.10
ubuntu Ready control-plane 4m41s v1.26.9+k0s 10.152.56.54 <none> Ubuntu 22.04.1 LTS 5.15.0-1013-raspi containerd://1.6.10
ubuntu@ubuntu:~$ sudo k0s kc get pod -owide -A
NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
kube-system kube-proxy-kkv2l 1/1 Running 0 4m44s 10.152.56.54 ubuntu <none> <none>
Expand Down Expand Up @@ -445,7 +445,7 @@ As this is a worker node, we cannot access the Kubernetes API via the builtin
```console
ubuntu@ubuntu:~$ sudo k0s status
Version: v1.26.8+k0s.0
Version: v1.26.9+k0s.0
Process ID: 1631
Role: worker
Workloads: true
Expand Down Expand Up @@ -497,7 +497,7 @@ Using the above kubeconfig, you can now access and use the cluster:
```console
ubuntu@ubuntu:~$ KUBECONFIG=/path/to/kubeconfig kubectl get nodes,deployments,pods -owide -A
NAME STATUS ROLES AGE VERSION INTERNAL-IP EXTERNAL-IP OS-IMAGE KERNEL-VERSION CONTAINER-RUNTIME
node/ubuntu Ready <none> 5m1s v1.26.8+k0s 10.152.56.54 <none> Ubuntu 22.04.1 LTS 5.15.0-1013-raspi containerd://1.6.10
node/ubuntu Ready <none> 5m1s v1.26.9+k0s 10.152.56.54 <none> Ubuntu 22.04.1 LTS 5.15.0-1013-raspi containerd://1.6.10
NAMESPACE NAME READY UP-TO-DATE AVAILABLE AGE CONTAINERS IMAGES SELECTOR
kube-system deployment.apps/coredns 1/1 1 1 33m coredns registry.k8s.io/coredns/coredns:v1.7.0 k8s-app=kube-dns
Expand Down
4 changes: 2 additions & 2 deletions docs/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,6 @@ The biggest new k0s features will typically only be delivered on top of the late

The k0s version string consists of the Kubernetes version and the k0s version. For example:

- v1.26.8+k0s.0
- v1.26.9+k0s.0

The Kubernetes version (1.26.8) is the first part, and the last part (k0s.0) reflects the k0s version, which is built on top of the certain Kubernetes version.
The Kubernetes version (1.26.9) is the first part, and the last part (k0s.0) reflects the k0s version, which is built on top of the certain Kubernetes version.
4 changes: 2 additions & 2 deletions docs/reset.md
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,8 @@ k0sctl can be used to connect each node and remove all k0s-related files and pro
INFO ==> Running phase: Prepare hosts
INFO ==> Running phase: Gather k0s facts
INFO [ssh] 13.53.43.63:22: found existing configuration
INFO [ssh] 13.53.43.63:22: is running k0s controller version 1.26.8+k0s.0
INFO [ssh] 13.53.218.149:22: is running k0s worker version 1.26.8+k0s.0
INFO [ssh] 13.53.43.63:22: is running k0s controller version 1.26.9+k0s.0
INFO [ssh] 13.53.218.149:22: is running k0s worker version 1.26.9+k0s.0
INFO [ssh] 13.53.43.63:22: checking if worker has joined
INFO ==> Running phase: Reset hosts
INFO [ssh] 13.53.43.63:22: stopping k0s
Expand Down
4 changes: 2 additions & 2 deletions docs/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ You can configure the desired cluster version in the k0sctl configuration by set
```yaml
spec:
k0s:
version: 1.26.8+k0s.0
version: 1.26.9+k0s.0
```
If you do not specify a version, k0sctl checks online for the latest version and defaults to it.
Expand All @@ -75,7 +75,7 @@ INFO[0027] [ssh] 10.0.0.17:22: waiting for node to become ready again
INFO[0027] [ssh] 10.0.0.17:22: upgrade successful
INFO[0027] ==> Running phase: Disconnect from hosts
INFO[0027] ==> Finished in 27s
INFO[0027] k0s cluster version 1.26.8+k0s.0 is now installed
INFO[0027] k0s cluster version 1.26.9+k0s.0 is now installed
INFO[0027] Tip: To access the cluster you can now fetch the admin kubeconfig using:
INFO[0027] k0sctl kubeconfig
```
4 changes: 2 additions & 2 deletions docs/worker-node-config.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ kubectl get node --show-labels

```shell
NAME STATUS ROLES AGE VERSION LABELS
worker0 NotReady <none> 10s v1.26.8+k0s beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,k0sproject.io/foo=bar,k0sproject.io/other=xyz,kubernetes.io/arch=amd64,kubernetes.io/hostname=worker0,kubernetes.io/os=linux
worker0 NotReady <none> 10s v1.26.9+k0s beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,k0sproject.io/foo=bar,k0sproject.io/other=xyz,kubernetes.io/arch=amd64,kubernetes.io/hostname=worker0,kubernetes.io/os=linux
```

Controller worker nodes are assigned `node.k0sproject.io/role=control-plane` and `node-role.kubernetes.io/control-plane=true` labels:
Expand All @@ -25,7 +25,7 @@ kubectl get node --show-labels

```shell
NAME STATUS ROLES AGE VERSION LABELS
controller0 NotReady control-plane 10s v1.26.8+k0s beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=worker0,kubernetes.io/os=linux,node.k0sproject.io/role=control-plane,node-role.kubernetes.io/control-plane=true
controller0 NotReady control-plane 10s v1.26.9+k0s beta.kubernetes.io/arch=amd64,beta.kubernetes.io/os=linux,kubernetes.io/hostname=worker0,kubernetes.io/os=linux,node.k0sproject.io/role=control-plane,node-role.kubernetes.io/control-plane=true
```

**Note:** Setting the labels is only effective on the first registration of the node. Changing the labels thereafter has no effect.
Expand Down
2 changes: 1 addition & 1 deletion embedded-bins/Makefile.variables
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ containerd_build_shim_go_cgo_enabled = 0
#containerd_build_go_ldflags =
containerd_build_go_ldflags_extra = "-w -s -extldflags=-static"

kubernetes_version = 1.26.8
kubernetes_version = 1.26.9
helm_version = 3.11.1
kubernetes_buildimage = $(golang_buildimage)
kubernetes_build_go_tags = "providerless"
Expand Down
Loading

0 comments on commit 412bee1

Please sign in to comment.