This was a valid point brought up by a copilot review in PR
defaultRegistry in podevaluator.go hard-codes the catalog prefix, but image prefixing elsewhere is driven by --default-image-prefix/runneroptions.GHCRImagePrefix. To avoid config drift (and ensure the “default registry” auth/TLS behavior stays aligned with the actual prefix in use).
We should consider deriving this from runneroptions.GHCRImagePrefix or wiring the configured DefaultImagePrefix into the auth checks in podManager instead of duplicating the string literal here.
This was a valid point brought up by a copilot review in PR
defaultRegistryin podevaluator.go hard-codes the catalog prefix, but image prefixing elsewhere is driven by--default-image-prefix/runneroptions.GHCRImagePrefix. To avoid config drift (and ensure the “default registry” auth/TLS behavior stays aligned with the actual prefix in use).We should consider deriving this from
runneroptions.GHCRImagePrefixor wiring the configuredDefaultImagePrefixinto the auth checks inpodManagerinstead of duplicating the string literal here.