Non-default --status-socket or --run-dir break autopilot

[kke]

Before creating an issue, make sure you've checked the following:

• [x] You are running the latest released version of k0s
• [x] Make sure you've searched for existing issues, both open and closed
• [x] Make sure you've searched for PRs too, a fix might've been merged already
• [x] You're looking at docs for the released version, "main" branch docs are usually ahead of released versions.

Platform

Version

1.34.2

Sysinfo

No response

What happened?

Setting --status-socket to anything but the default value will break autopilot, which is hardcoded to connect to the default path. Same happens if you set a custom run-dir as the default socket path is based on run dir, but autopilot has hardcoded it as /run/k0s/status.sock.

Steps to reproduce

1. Start with --status-socket=/tmp/foo
2. Enable autopilot

Expected behavior

Autopilot works.

Actual behavior

Autopilot does not work.

Screenshots and logs

No response

Additional context

https://github.com/k0sproject/k0s/blob/c0998466cdf0752bdf3d601a973265790974097b/pkg/autopilot/controller/setup.go#L204