ci: harden IPFS publish pod staging#552
Merged
Merged
Conversation
lthibault
force-pushed
the
lthibault/ipfs-publish-kubectl-retry
branch
from
1c01aa5 to
91e1dec
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
kubectl cpinternally and use a longer main kubectl timeout for slow k3s API behaviorWhy
The first master run after #551 failed before
CID=with repeatedcontext deadline exceededwhile runningPublish to IPFS via VPS. IPNS was not updated and no managed stale unpins ran. This follow-up keeps the pin lifecycle behavior intact while making the pod staging/copy path less brittle and more diagnosable.Tests
bash tests/test_ipfs_release_publish.shshellcheck scripts/ipfs_publish_release.sh tests/test_ipfs_release_publish.shactionlint .github/workflows/rust.ymlgit diff --check