Repository navigation
fix(k8s): pin cloudflared-tunnel to v0.27 - #50
Merged
Merged
Conversation
Floating :latest with Always pulled whatever CI last pushed on any pod restart. v0.27 is the digest already running (3f08847e). Co-authored-by: Cursor <cursoragent@cursor.com>
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
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.


Pins
cloudflared-tunnelfrom:latest+Alwaystov0.27+IfNotPresent.v0.27(sha256:3f08847ee35d…) is the exact digest that was running, so this is a no-op rollout. Already applied live on prd-apps (kubectl apply -f k8s/cloudflared-tunnel-deployment.yaml); new pod registered 4 tunnel connections andhc.dataknife.airesponds.Prevents node reboots from silently rolling the tunnel to whatever CI last pushed as
latest(currently v0.29).Made with Cursor