After a reboot the cluster is broken

[scorputty]

It seems that even with a "clean shutdown" the cluster won't start proper. "hyperkube[2903]: E0530 05:55:32.206071 2903 kubelet.go:2466] "Error getting node" err="node "sno-laptop.mydomain.net" not found""

Any idea why this happens? I've done a reboot before and the cluster came up without issues but today it did not anymore.

[ryannix123]

Hi!

I recently uncovered this issue, and it has to do with the way Kubernetes rotates certificates every 16 to 22 hours. My suggestion is to leave your SNO instance running for 22 hours before shutting it down for an extended period.

https://access.redhat.com/solutions/4271712

I plan on updating this repo very soon, and I'll include a shell script that will output cert expirations.

• Ryan

[scorputty]

Ahh that makes sense, I suspected the certificates where the issue. Thanks, I will try this. Stephan.

…

On Tue, May 31, 2022 at 1:55 PM Ryan T Nix ***@***.***> wrote: Hi! I recently uncovered this issue, and it has to do with the way Kubernetes rotates certificates every 16 to 22 hours. My suggestion is to leave your SNO instance running for 22 hours before shutting it down for an extended period. https://access.redhat.com/solutions/4271712 I plan on updating this repo very soon, and I'll include a shell script that will output cert expirations. - Ryan — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFZC3M6TVRX42C67FPLYADVMX44RANCNFSM5XJMUY5A> . You are receiving this because you authored the thread.Message ID: ***@***.***>