You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I observe a weird behavior. Keel does not update one of the deployments, because it has authentication issues with GCR. After restart I get a log line stating, that the current digest is the one from the registry, while the pod is clearly running with an older image:
I observe a weird behavior. Keel does not update one of the deployments, because it has authentication issues with GCR. After restart I get a log line stating, that the current digest is the one from the registry, while the pod is clearly running with an older image:
time="2023-05-11T12:31:21Z" level=debug msg="trigger.poll.WatchTagJob: checking digest" current_digest="sha256:ff7f7e3ad0a305229ed89158a5d0ff6a7d513f921034c0eea82f09dbd64501dd" image="xyz:main" new_digest="sha256:ff7f7e3ad0a305229ed89158a5d0ff6a7d513f921034c0eea82f09dbd64501dd" registry_url="https://eu.gcr.io"
I think that the line below might be the issue and the digest should be pulled from k8s instead of the registry initially.
keel/trigger/poll/watcher.go
Line 274 in f8dabdc
Thanks
The text was updated successfully, but these errors were encountered: