Skip to content

Conversation

@olix0r
Copy link
Member

@olix0r olix0r commented Dec 5, 2024

The k3s release index may be updated before container images are available to use. This change updates the sync-k3s-images recipe to fail if any release images cannot be found. The CI workflow is updated to allow failures. The workflow fails if the sync recipe modifies the cached image digests.

The k3s release index may be updated before container images are available to
use. This change updates the sync-k3s-images recipe to fail if any release images
cannot be found. The CI workflow is updated to allow failures. The workflow fails
if the sync recipe modifies the cached image digests.
- uses: actions/checkout@9bb56186c3b09b4f86b1c65136769dd318469633
- uses: ./actions/setup-tools
- run: just sync-k3s-images
# The sync may fail when a new K3s version is released. This is expected.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we keep the continue-on-error: true above if this suppresses the error from an updated version?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. Since this can fail in general when there are new k3s versions available, we don't want to cancel other workflows just because a new file is generated. It's mostly an advisory check so, when we're doing a new version, for instance, we ensure we've run the sync. This was just a specific weird corner case where the sync would yield an unusable manifest.

@olix0r olix0r merged commit 90e894c into main Dec 5, 2024
25 checks passed
@olix0r olix0r deleted the ver/sync-fail branch December 5, 2024 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants