Add --no-autoupdate flag for cloudflare-tunnel-remote #51
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.
It seems that the
cloudflare-tunnel-remotehelm chart is missing the--no-autoupdateflag which is added to the default image in the entrypoint looking at the image layer:This results in
cloudflaredcrashing everytime there is a new update. Looking at the logs of the pods stuck in crashbackloopoff:It seems that it restarts itself once the update is finished, but since this is a pod, Kubernetes will restart it with the same configuration and
cloudflaredwill be stuck in the same loop forever:With this PR, the update will be shown in the logs as a warning and the pods will no longer be stuck in crashbackloopoff: