Skip to content

v1.24.11+rke2r1
Compare
Choose a tag to compare
@brooksn brooksn released this 10 Mar 17:27
· 79 commits to release-1.24 since this release
v1.24.11+rke2r1
23bdc98
This commit was created on github.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

This release updates Kubernetes to v1.24.11, and fixes a number of issues.

Important Note

If your server (control-plane) nodes were not started with the --token CLI flag or config file key, a randomized token was generated during initial cluster startup. This key is used both for joining new nodes to the cluster, and for encrypting cluster bootstrap data within the datastore. Ensure that you retain a copy of this token, as is required when restoring from backup.

You may retrieve the token value from any server already joined to the cluster:

cat /var/lib/rancher/rke2/server/token

Changes since v1.24.10+rke2r1:

  • Don't handle kube-proxy in static pod cleanup (#3836)
  • Bump cilium images (#3826)
  • Update canal chart to v3.25.0-build2023020901 (#3885)
  • Remove pod logs as part of killall (#3868)
  • Bump wharfie and go-containerregistry (#3865)
  • Update Calico to v3.25.0 (#3891)
  • Bump k3s version (#3899)
    • Fixed an issue where leader-elected controllers for managed etcd did not run on etcd-only nodes
    • RKE2 now functions properly when the cluster CA certificates are signed by an existing root or intermediate CA. You can find a sample script for generating such certificates before RKE2 starts in the K3s repo at contrib/util/certs.sh.
    • RKE2 now supports kubeadm style join tokens. rke2 token create now creates join token secrets, optionally with a limited TTL.
    • RKE2 agents joined with an expired or deleted token stay in the cluster using existing client certificates via the NodeAuthorization admission plugin, unless their Node object is deleted from the cluster.
    • ServiceLB now honors the Service's ExternalTrafficPolicy. When set to Local, the LoadBalancer will only advertise addresses of Nodes with a Pod for the Service, and will not forward traffic to other cluster members. (ServiceLB is still disabled by default)
  • Bump K3s commit (#3907)
  • Add bootstrap token auth handler (#3922)
  • Update to kubernetes v1.24.11 (#3950)

Packaged Component Versions

Component Version
Kubernetes v1.24.11
Etcd v3.5.4-k3s1
Containerd v1.6.15-k3s1
Runc v1.1.4
Metrics-server v0.6.2
CoreDNS v1.9.3
Ingress-Nginx 4.1.0
Helm-controller v0.13.1

Available CNIs

Component Version FIPS Compliant
Canal (Default) Flannel v0.21.1
Calico v3.25.0		 Yes
Calico v3.25.0 No
Cilium v1.12.5 No
Multus v3.9.3 No

Helpful Links

As always, we welcome and appreciate feedback from our community of users. Please feel free to:

Assets 52
Loading