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
In some cases, like controllers/operators etc, we might not know all the dependencies as far as images, even after using the provided tools like zarf dev find-images. In our case, we found images that were dependencies but what what repo we should be point to. The initial attempts were pointing at a repo that didnt match what the pod expected, but we couldnt see that due to the mutating webhook effect on the pods spec.
Adding a label or annotation to the pods which would state the original image repo, version, and name that the pods would be looking for before the mutating webhook changed it to point to the internal image repo would be useful. This would make it extremely easy to find what images are missing and add those missing images to their zarf.yaml.
Discussed in your discord, I originally thought there might be a command to reverse the UID, but its a one way hash so options are limited. Alternate option which I will add here for historical value, was given in the discord which is helpful:
"You can check if an image name you have matches the hash through the command zarf internal crc32 my_image at least"
The text was updated successfully, but these errors were encountered:
In some cases, like controllers/operators etc, we might not know all the dependencies as far as images, even after using the provided tools like
zarf dev find-images
. In our case, we found images that were dependencies but what what repo we should be point to. The initial attempts were pointing at a repo that didnt match what the pod expected, but we couldnt see that due to the mutating webhook effect on the pods spec.Adding a label or annotation to the pods which would state the original image repo, version, and name that the pods would be looking for before the mutating webhook changed it to point to the internal image repo would be useful. This would make it extremely easy to find what images are missing and add those missing images to their zarf.yaml.
Discussed in your discord, I originally thought there might be a command to reverse the UID, but its a one way hash so options are limited. Alternate option which I will add here for historical value, was given in the discord which is helpful:
"You can check if an image name you have matches the hash through the command
zarf internal crc32 my_image
at least"The text was updated successfully, but these errors were encountered: