Skip to content

Releases: rancher/rke2

v1.19.8-rc3+rke2r1

25 Feb 20:10
77ad545
Compare
Choose a tag to compare
v1.19.8-rc3+rke2r1 Pre-release
Pre-release
Merge pull request #732 from erikwilson/release-1.19

Upgrade helm-controller / klipper-helm

v1.19.8-rc2+rke2r1

24 Feb 23:09
459472a
Compare
Choose a tag to compare
v1.19.8-rc2+rke2r1 Pre-release
Pre-release
Merge pull request #725 from erikwilson/update-hardened-images

Update hardened images

v1.19.8-rc1+rke2r1

20 Feb 02:08
4c1f873
Compare
Choose a tag to compare
v1.19.8-rc1+rke2r1 Pre-release
Pre-release
Merge pull request #709 from erikwilson/k8s-v1.19.8

Update to k8s v1.19.8

v1.18.16+rke2r1

24 Feb 15:41
fb4b876
Compare
Choose a tag to compare

This release updates Kubernetes to v1.18.16
For more details on what's new, see the Kubernetes release notes

Changes since v1.18.15+rke2r1

Packaged Component Versions

Component Version
Kubernetes v1.18.16
Etcd v3.4.13-k3s1
Containerd v1.3.9-k3s1
Runc v1.0.0-rc92
CNI Plugins v0.8.7
Flannel v0.13.0-rancher1
Calico v3.13.3
Metrics-server v0.3.6
CoreDNS v1.6.9
Ingress-Nginx v1.36.3
Helm-controller v0.7.3

Known Issues

  • Helm-controller sometimes leave behind failed install job pods with reason "NodeAffinity". This is due to an upstream issue. This is harmless as the pods will be recreated and eventually succeed, but the failed pods will remain until manually deleted. #127

This will be addressed in an upcoming release.

Helpful Links

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

v1.18.16-rc1+rke2r1

20 Feb 02:12
fb4b876
Compare
Choose a tag to compare
v1.18.16-rc1+rke2r1 Pre-release
Pre-release
Merge pull request #713 from erikwilson/k8s-v1.18.16

Update to k8s v1.18.16

v1.20.2-beta1+rke2r1

02 Feb 20:42
Compare
Choose a tag to compare
v1.20.2-beta1+rke2r1 Pre-release
Pre-release

This is an out-of-cycle beta release to make artifacts available for testing fixes to AppArmor. We do not plan to release v1.20.2+rke2r1; the next production release on this branch will be made against Kubernetes v1.20.3.

v1.19.7-beta1+rke2r2

02 Feb 19:53
Compare
Choose a tag to compare
v1.19.7-beta1+rke2r2 Pre-release
Pre-release

This is an out-of-cycle beta release to make artifacts available for testing fixes to AppArmor. We do not plan to release v1.19.7+rke2r2; the next production release on this branch will be made against Kubernetes v1.19.8.

v1.19.7+rke2r1

20 Jan 01:50
Compare
Choose a tag to compare

This release updates Kubernetes to v1.19.7
For more details on what's new, see the Kubernetes release notes

Changes since v1.19.5+rke2r1

Packaged Component Versions

Component Version
Kubernetes v1.19.7
Etcd v3.4.13-k3s1
Containerd v1.4.3-k3s2
Runc v1.0.0-rc92
CNI Plugins v0.8.7
Flannel v0.13.0-rancher1
Calico v3.13.3
Metrics-server v0.3.6
CoreDNS v1.6.9
Ingress-Nginx v1.36.3
Helm-controller v0.8.3

Known Issues

  • Helm-controller sometimes leave behind failed install job pods with reason "NodeAffinity". This is due to an upstream issue. This is harmless as the pods will be recreated and eventually succeed, but the failed pods will remain until manually deleted. #127

This will be addressed in an upcoming release.

Helpful Links

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

v1.19.7-rc1+rke2r1

15 Jan 22:44
7c7c64e
Compare
Choose a tag to compare
v1.19.7-rc1+rke2r1 Pre-release
Pre-release
update Kubernetes to v1.19.7 (#666)

* update Kubernetes to v1.19.7

v1.18.15+rke2r1

20 Jan 02:02
44a0b3f
Compare
Choose a tag to compare

This release updates Kubernetes to v1.18.15
For more details on what's new, see the Kubernetes release notes

Changes since v1.18.13+rke2r1

Packaged Component Versions

Component Version
Kubernetes v1.18.15
Etcd v3.4.13-k3s1
Containerd v1.4.3-k3s2
Runc v1.0.0-rc92
CNI Plugins v0.8.7
Flannel v0.13.0-rancher1
Calico v3.13.3
Metrics-server v0.3.6
CoreDNS v1.6.9
Ingress-Nginx v1.36.3
Helm-controller v0.8.3

Known Issues

  • Helm-controller sometimes leave behind failed install job pods with reason "NodeAffinity". This is due to an upstream issue. This is harmless as the pods will be recreated and eventually succeed, but the failed pods will remain until manually deleted. #127

This will be addressed in an upcoming release.

Helpful Links

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