Bot releases are hidden (Show)
The daemon image contains a 1.28.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.27.x, 1.28.x and 1.29.x
Thanks a lot to everyone who contributed to kured since 1.15.0.
Published by ckotzbauer 9 months ago
Due to the changes made for the new signal
reboot-mode to reduce needed permissions of kured, the default
sentinel path and its mounting have changed. If you are using our YAML-Manifests instead of the helm-chart
please ensure to update the full manifest instead of only increasing the version-number.
There are two manifest-variants in the repo available now: kured-ds.yaml
with the "old" reboot-command mechanism and the new
kured-ds-signal.yaml
manifest which uses the new reboot-signal mechanism with non-privileged permissions.
The daemon image contains a 1.28.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.27.x, 1.28.x and 1.29.x
Thanks a lot to everyone who contributed to kured since 1.14.2.
Published by dholbach 11 months ago
The daemon image contains a 1.27.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.26.x, 1.27.x and 1.28.x
Thanks a lot to everyone who contributed to kured since 1.14.1.
Full Changelog: https://github.com/kubereboot/kured/compare/1.14.1...1.14.2
Published by dholbach 12 months ago
The daemon image contains a 1.27.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.26.x, 1.27.x and 1.28.x
Thanks a lot to everyone who contributed to kured since 1.14.0.
Full Changelog: https://github.com/kubereboot/kured/compare/1.14.0...1.14.1
Published by ckotzbauer about 1 year ago
The daemon image contains a 1.27.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.26.x, 1.27.x and 1.28.x
Thanks a lot to everyone who contributed to kured since 1.13.2.
Published by ckotzbauer about 1 year ago
The daemon image contains a 1.26.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.25.x, 1.26.x and 1.27.x
Thanks a lot to everyone who contributed to kured since 1.13.1.
Published by dholbach over 1 year ago
The daemon image contains a 1.26.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.25.x, 1.26.x and 1.27.x
Thanks a lot to everyone who contributed to kured since 1.13.0.
Published by ckotzbauer over 1 year ago
nodeSelector
for kubernetes.io/os: linux
The daemon image contains a 1.25.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.25.x, 1.26.x and 1.27.x
Thanks a lot to everyone who contributed to kured since 1.12.2.
Published by ckotzbauer over 1 year ago
This patch release only contains dependency updates, which should make your CVE checker happy again.
The daemon image contains a 1.25.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.24.x, 1.25.x and 1.26.x
Thanks a lot to everyone who contributed to kured since 1.12.1.
Published by dholbach over 1 year ago
This patch release only contains dependency updates, which should make your CVE checker happy again.
The daemon image contains a 1.25.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.24.x, 1.25.x and 1.26.x
Thanks a lot to everyone who contributed to kured since 1.12.0.
Published by ckotzbauer almost 2 years ago
The daemon image contains a 1.25.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.24.x, 1.25.x and 1.26.x
Thanks a lot to everyone who contributed to kured since 1.11.0. Commits from @dholbach
Published by ckotzbauer almost 2 years ago
The daemon image contains a 1.24.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.23.x, 1.24.x and 1.25.x
Thanks a lot to everyone who contributed to kured since 1.10.2. Commits from @dholbach, @evrardjp, @ckotzbauer
Published by ckotzbauer about 2 years ago
The daemon image contains a 1.23.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.22.x, 1.23.x and 1.24.x
Thanks a lot to everyone who contributed to kured since 1.10.1. Commits from @jackfrancis, @kingdonb, @dholbach, @ckotzbauer
Published by ckotzbauer over 2 years ago
The daemon image contains a 1.23.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.22.x, 1.23.x and 1.24.x
Thanks a lot to everyone who contributed to kured since 1.10.0. Commits from @atighineanu, @dholbach, @ckotzbauer
Published by ckotzbauer over 2 years ago
With this release kured will retry to cordon and uncordon a node in case it fails.
This should prevent nodes from being "Unschedulable" forever. Also kured will hold the node-lock until uncordoning
and the lock-release succeeded to avoid reproducing the same issue everywhere. See #486 for more details.
The daemon image contains a 1.23.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.22.x, 1.23.x and 1.24.x
Thanks a lot to everyone who contributed to kured since 1.9.2. Commits from @atighineanu, @Garnaalkroket, @losil, @davideshay, @liger1978, @elchenberg, @jackfrancis, @ckotzbauer
Published by ckotzbauer over 2 years ago
The daemon image contains a 1.22.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.21.x, 1.22.x and 1.23.x
Thanks a lot to everyone who contributed to kured since 1.9.1. Commits from @bambriy, @khuedoan, @weseven, @ckotzbauer
Published by ckotzbauer almost 3 years ago
The daemon image contains a 1.22.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.21.x, 1.22.x and 1.23.x
Thanks a lot to everyone who contributed to kured since 1.9.0. Commits from @dkulchinsky, @ckotzbauer
Published by ckotzbauer almost 3 years ago
The daemon image contains a 1.22.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.21.x, 1.22.x and 1.23.x
Thanks a lot to everyone who contributed to kured since 1.9.0. Commits from @georgekaz, @dkulchinsky, @dholbach, @ckotzbauer
Published by dholbach almost 3 years ago
1.8.1
was only half-released - so here the changelog for all changes since 1.8.0
.
No breaking changes, but you might want to double-check and review https://containrrr.dev/shoutrrr/v0.5/services/overview/ though to make sure you got your notify-url
(new) or slack-hook-url
(old) correct. See #368 for more detail.
This commit introduces a new flag '--log-format' that allows a user
to configure json logging on the pods. If the log-format
is not specified, the formatter will default to the existing
text formatter.
The daemon image contains a 1.21.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.20.x, 1.21.x and 1.22.x
Thanks a lot to everyone who contributed to kured since 1.8.0. Commits from @MattJeanes @amorey @atighineanu @ckotzbauer @dholbach Daniel Kvist @jackfrancis @evrardjp
Published by ckotzbauer about 3 years ago
reboot-delay
command line argument #418The daemon image contains a 1.21.x k8s.io/{client-go,kubectl} for the purposes of maintaining the lock and draining worker nodes. Kubernetes aims to provide forwards & backwards compatibility of one minor version between client and server, so this should work on 1.20.x, 1.21.x and 1.22.x
Thanks a lot to everyone who contributed to kured since 1.7.0. Commits from @piksel, @amorey, @jackfrancis, @dkulchinsky, @dhoeld, @MattJeanes, @evrardjp, @renaudhager, @SimeonPoot, @spingel, @atighineanu, @dholbach, @ckotzbauer