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
It would be convenient if the version check was not so strict when specifying a local k0s binary. It may be inconvenient to figure out the exact k0s version if you run k0sctl on MacOS or architecture that differs from the k0s architecture.
Here is an attempt to deploy an amd64 k0s binary built from git from using a MacOS/arm64 k0sctl host.
INFO ==> Running phase: Set k0s version
INFO Looking up latest stable k0s version
INFO Using k0s version v1.30.2+k0s.0
INFO ==> Running phase: Connect to hosts
INFO [ssh] 10.0.0.24:22: connected
INFO ==> Running phase: Detect host operating systems
INFO [ssh] 10.0.0.24:22: is running Alpine Linux edge
INFO ==> Running phase: Acquire exclusive host lock
INFO ==> Running phase: Prepare hosts
INFO ==> Running phase: Gather host facts
INFO [ssh] 10.0.0.24:22: using ncopa-desktop as hostname
INFO [ssh] 10.0.0.24:22: discovered eth0 as private interface
INFO [ssh] 10.0.0.24:22: discovered 172.21.1.2 as private address
INFO ==> Running phase: Validate hosts
INFO ==> Running phase: Validate facts
INFO ==> Running phase: Download k0s binaries to local host
INFO ==> Running phase: Upload k0s binaries to hosts
INFO [ssh] 10.0.0.24:22: uploading k0s binary from ./k0s to /usr/local/bin/k0s.tmp.1721230260080085000
INFO ==> Running phase: Install k0s binaries on hosts
INFO * Running clean-up for phase: Acquire exclusive host lock
INFO * Running clean-up for phase: Install k0s binaries on hosts
INFO [ssh] 10.0.0.24:22: cleaning up k0s binary tempfile
INFO ==> Apply failed
FATA apply failed - log file saved to /Users/ncopa/Library/Caches/k0sctl/k0sctl.log: failed on 1 hosts:
- [ssh] 10.0.0.24:22: failed to install k0s binary: updated k0s binary version is v1.30.0+k0s.0-319-gc578d7fc1 not v1.30.2+k0s.0
Would be nice if the version check is skipped when specifying k0sBinaryPath so we dont need qemu to find the k0s version to make k0sctl happy.
The text was updated successfully, but these errors were encountered:
It would be convenient if the version check was not so strict when specifying a local k0s binary. It may be inconvenient to figure out the exact k0s version if you run k0sctl on MacOS or architecture that differs from the k0s architecture.
Here is an attempt to deploy an amd64 k0s binary built from git from using a MacOS/arm64 k0sctl host.
Would be nice if the version check is skipped when specifying
k0sBinaryPath
so we dont need qemu to find the k0s version to make k0sctl happy.The text was updated successfully, but these errors were encountered: