Open laverya opened 4 months ago
Also, incidentally, the autopilot docs are kind of lacking and don't actually say that AirgapUpdate is for updating the image file - I'm assuming that I'm using this for its intended purpose here? 😅
That is correct assumption.
The issue is marked as stale since no activity has been recorded in 30 days
Should we implement an out-of-band process to cleanup these redundant image bundles, or is that something we should try to include within k0s?
I'll have a look if there's an easy way to make Autopilot replace that file.
The issue is marked as stale since no activity has been recorded in 30 days
The issue is marked as stale since no activity has been recorded in 30 days
We're starting to come back around to this, so it would be great to know if this file can be replaced or if we'll have to implement some cleanup ourselves.
Before creating an issue, make sure you've checked the following:
Platform
Version
v1.28.7+k0s.0
Sysinfo
`k0s sysinfo`
What happened?
When using
AirgapUpdate
to pull a new images file for a host, the name of the file was the same as the file currently on the host (images-amd64.tar
). This causes theAirgapUpdate
to fail with a content length error?Steps to reproduce
X.tar
X.tar
Expected behavior
The new image file is downloaded and replaces the current image file.
Actual behavior
No new image file is downloaded, instead the autopilot plan fails, with the proximate log line being
Screenshots and logs
From
journalctl -u k0scontroller.service
The plan yaml:
We run a server (outside of k0s) on localhost in order to serve these files.
Additional context
Our workaround here will be to just change the name of the images file each update, but then we need to handle cleanup too - is there something we should be doing instead? For the
k0s
binary we can just always name itk0s-upgrade
and it will be renamed as part of the upgrade process, but that doesn't appear to be the case for this file.(this is also not the latest version of k0s, as that is a necessity for testing updates... I can trigger the AirgapUpdate plan component on its own if that would be desirable though)