Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] Make k3s compatible to be run as a service on Windows OS #9298

Open
Tracked by #9313
caroline-suse-rancher opened this issue Jan 25, 2024 · 1 comment
Open
Tracked by #9313
Labels
area/windows kind/enhancement An improvement to existing functionality priority/high

Comments

@caroline-suse-rancher
Copy link
Contributor

caroline-suse-rancher commented Jan 25, 2024

Generally, k3s should be able to be run as a service. In the current implementation of k3s for Windows in this issue, this isn't a capability. Ideally, it should be and the service should be available for installation via a script, similar to what we offer on linux.

@brandond
Copy link
Member

brandond commented Feb 11, 2025

Rather than having K3s manage installing itself as a Windows service (as RKE2 does) we should document or automate use of NSSM as a service wrapper: https://community.chocolatey.org/packages/nssm

Despite the somewhat silly name this is a GREAT project, I wish we'd used it for RKE2 instead of rolling our own Windows service management code.

Edit: Apparently NSSM is no longer maintained. I guess we should use something else. Regardless we should not roll our own service management and repeat the issues we have run into with logging and service management for RKE2 on windows.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/windows kind/enhancement An improvement to existing functionality priority/high
Projects
Status: Accepted
Development

No branches or pull requests

2 participants