The image metadata "cache" stores its data with keys that include a username, with the idea being that this will avoid leaking information when images have different authentication.
As things stand, however, the username is always an empty string when putting image metadata in the cache, because it's derived from an unassigned Credentials field in the cache warmer. And it's always an empty string when looking up image metadata, because it is given a literal empty Credentials value.
Either these should be fixed to use the actual credentials (e.g., by always finding the imagePullSecret when looking up controllers), or we should just remove the username from the key (or otherwise give up on segregating image metadata).
The image metadata "cache" stores its data with keys that include a username, with the idea being that this will avoid leaking information when images have different authentication.
As things stand, however, the username is always an empty string when putting image metadata in the cache, because it's derived from an unassigned Credentials field in the cache warmer. And it's always an empty string when looking up image metadata, because it is given a literal empty Credentials value.
Either these should be fixed to use the actual credentials (e.g., by always finding the imagePullSecret when looking up controllers), or we should just remove the username from the key (or otherwise give up on segregating image metadata).