Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assuming registry up-to-date status? #724

Open
zaks opened this issue May 11, 2023 · 0 comments
Open

Assuming registry up-to-date status? #724

zaks opened this issue May 11, 2023 · 0 comments

Comments

@zaks
Copy link

zaks commented May 11, 2023

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.

job := NewWatchTagJob(w.providers, w.registryClient, details)

Thanks

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

No branches or pull requests

1 participant