How to Install and Uninstall kured Package on openSuSE Tumbleweed
Last updated: November 07,2024
1. Install "kured" package
This tutorial shows how to install kured on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
kured
Copied
2. Uninstall "kured" package
In this section, we are going to explain the necessary steps to uninstall kured on openSuSE Tumbleweed:
$
sudo zypper remove
kured
Copied
3. Information about the kured package on openSuSE Tumbleweed
Information for package kured:
------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : kured
Version : 1.10.2-3.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 50.4 MiB
Installed : No
Status : not installed
Source package : kured-1.10.2-3.1.src
Upstream URL : https://github.com/weaveworks/kured
Summary : Kubernetes daemonset to perform safe automatic node reboots
Description :
Kured (KUbernetes REboot Daemon) is a Kubernetes daemonset that
performs safe automatic node reboots when the need to do so is
indicated by the package management system of the underlying OS.
- Watches for the presence of a reboot sentinel e.g. /var/run/reboot-required
- Utilises a lock in the API server to ensure only one node reboots at a time
- Optionally defers reboots in the presence of active Prometheus alerts
- Cordons & drains worker nodes before reboot, uncordoning them after
------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : kured
Version : 1.10.2-3.1
Arch : x86_64
Vendor : openSUSE
Installed Size : 50.4 MiB
Installed : No
Status : not installed
Source package : kured-1.10.2-3.1.src
Upstream URL : https://github.com/weaveworks/kured
Summary : Kubernetes daemonset to perform safe automatic node reboots
Description :
Kured (KUbernetes REboot Daemon) is a Kubernetes daemonset that
performs safe automatic node reboots when the need to do so is
indicated by the package management system of the underlying OS.
- Watches for the presence of a reboot sentinel e.g. /var/run/reboot-required
- Utilises a lock in the API server to ensure only one node reboots at a time
- Optionally defers reboots in the presence of active Prometheus alerts
- Cordons & drains worker nodes before reboot, uncordoning them after