From kured version 5.4.1 the reboot sentinel flags are begin ignored on installation. When doing helm get values on kubereboot values are there but ignored in the daemonset.
reboot-sentinel set to /sentinel/reboot-required but in the values.yaml file set to /var/run/reboot-required
reboot-sentinel-command ignored but in values.yaml file set to sh -c "! needs-restarting --reboothint"
From kured version 5.4.1 the reboot sentinel flags are begin ignored on installation. When doing helm get values on kubereboot values are there but ignored in the daemonset.
reboot-sentinel set to /sentinel/reboot-required but in the values.yaml file set to /var/run/reboot-required reboot-sentinel-command ignored but in values.yaml file set to sh -c "! needs-restarting --reboothint"
USER-SUPPLIED VALUES: configuration: annotateNodes: true concurrency: "1" drainGracePeriod: "-1" drainTimeout: "0" endTime: "16:00" forceReboot: false lockReleaseDelay: 0 logFormat: text messageTemplateDrain: Draining node %s messageTemplateReboot: Rebooting node %s messageTemplateUncordon: Node %s rebooted & uncordoned successfully! period: 5m preferNoScheduleTaint: weave.works/kured-node-reboot rebootCommand: /bin/systemctl reboot rebootDays:
Daemonset configuration: template: metadata: creationTimestamp: null labels: app.kubernetes.io/instance: kubereboot app.kubernetes.io/managed-by: Helm app.kubernetes.io/name: kured helm.sh/chart: kured-5.4.1 spec: containers: