Pulling older images when the new pod creation got triggered

[Madhu-mohan86]

Here is my the policy i have used in annotations :

annotations:
    keel.sh/policy: minor
    keel.sh/trigger: poll
    keel.sh/approved: "true"

I have also watched for keel logs and it says ,

time="2024-08-16T05:07:32Z" level=info msg="auth successful for user admin"
time="2024-08-16T07:59:52Z" level=info msg="trigger.poll.RepositoryWatcher: new watch tag digest job added" digest="sha256:4f900aaeb8c9ed68b2626d0c16aaf5e0e844b8844ad089f687e3eba14d28f2ae" image="techeunimart/reacttesting:latest" job_name="index.docker.io/techeunimart/reacttesting:latest" schedule="@every 1m"

so when I want to check for its working , I have updated the dockerfile rebuilt it and pushed to the registry , guess what the keel actually detects the checksum change and triggers the new update the logs are found as :

time="2024-08-16T08:33:53Z" level=info msg="trigger.poll.WatchTagJob: digest change detected, submiting event to providers" image="techeunimart/reacttesting:latest" new_digest="sha256:887b01e2126e76985312c26d39597a8d124ee442a5cbc555555103f4c7515a81"
time="2024-08-16T08:33:53Z" level=warning msg="provider.kubernetes: got error while archiving approvals counter after successful update" error="approval not found: record not found" kind=deployment name=reactdply namespace=default
time="2024-08-16T08:33:53Z" level=info msg="provider.kubernetes: resource updated" kind=deployment name=reactdply namespace=default new=latest previous=latest

for cross verification I also retrieved of the k8s cluster :

98s         Normal    Killing                 pod/reactdply-578d7d567-h2q42                             Stopping container reactdply
98s         Normal    Created                 pod/reactdply-5b7757cc4d-bksd4                            Created container reactdply
98s         Normal    Started                 pod/reactdply-5b7757cc4d-bksd4                            Started container reactdply
98s         Normal    Pulled                  pod/reactdply-5b7757cc4d-bksd4                            Successfully pulled image "techeunimart/reacttesting:latest" in 131ms (131ms including waiting)
98s         Normal    Pulling                 pod/reactdply-5b7757cc4d-bksd4                            Pulling image "techeunimart/reacttesting:latest"
98s         Normal    SuccessfulDelete        replicaset/reactdply-578d7d567                            Deleted pod: reactdply-578d7d567-h2q42
98s         Normal    ScalingReplicaSet       deployment/reactdply                                      Scaled down replica set reactdply-578d7d567 to 0 from 1

now when i inspect newly created it gives the checksum of older one which means keel is actually doing its job but it is pulling up the older image and doesn't reflect changes that we required the inspection logs are

  "containerID": "containerd://3d0814b6a38dd553356de1272a00f9914392c1b407a4854277c9704ede8441db",
  "image": "docker.io/techeunimart/reacttesting:latest",
  "imageID": "docker.io/techeunimart/reacttesting@sha256:4f900aaeb8c9ed68b2626d0c16aaf5e0e844b8844ad089f687e3eba14d28f2ae",

This is the issue or bug I found as when working with keel may be my configuration is missing but I provided all from my side