You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 8, 2023. It is now read-only.
Currently K3OS embeds all the minimal requirements of an OS to interact with hardware.
However power supply should also be incorporated into the OS to prevent power default by shutting down correctly the system.
Then is there a way to embed NUT alpine package into the K3OS distribution?
The text was updated successfully, but these errors were encountered:
But how to integrate operating system level support for this?
Do I have to use config.yaml -> write_files to make a custom /etc/init.d service to look for a hostpath file created via a Pod?
Or is it possible for a pod to mount a hostPath to /etc/killpower ? ( I did a grep in /etc for killpower and I don't think anything is looking for that file?)
Or is there anyway for a Pod to execute k3s-killall.sh and poweroff on the Node? (there doesn't even seem to be much information on the internet about how to properly shutdown kubernetes, i assume k3s-killall.sh and poweroff is required?)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently K3OS embeds all the minimal requirements of an OS to interact with hardware.
However power supply should also be incorporated into the OS to prevent power default by shutting down correctly the system.
Then is there a way to embed NUT alpine package into the K3OS distribution?
The text was updated successfully, but these errors were encountered: