I created a Warehouse pointing to an image on a private registry, exposed on a custom port. The image url was my.registry.url:10000/path/to/image. I created a generic credentials Secret with repoURLIsRegex: "true" and repoURL: "my.registry.url:10000/.*", expecting Kargo to associate the credentials to the image, but it was not so.
I temporarily solved the problem by changing the regex to "my.registry.url.10000/.*", as I suspect that the normalizations done here change the examined image url to my.registry.url/10000/path/to/image, causing the original regex to not match.
Steps to Reproduce
Set Kargo log level to debug
Create, in a Kargo Project, a Warehouse with a subscription to an image with url my.registry.url:10000/path/to/image
Create a credentials Secret for such Warehouse with repoURLIsRegex: "true" and repoURL: "my.registry.url:10000/.*"
See how Kargo logs "found no credentials for image repo" when refreshing the Warehouse
Change the repo url in the Secret to repoURL: "my.registry.url.10000/.*"
Description
I created a Warehouse pointing to an image on a private registry, exposed on a custom port. The image url was
my.registry.url:10000/path/to/image. I created a generic credentials Secret withrepoURLIsRegex: "true"andrepoURL: "my.registry.url:10000/.*", expecting Kargo to associate the credentials to the image, but it was not so.I temporarily solved the problem by changing the regex to "my.registry.url.10000/.*", as I suspect that the normalizations done here change the examined image url to
my.registry.url/10000/path/to/image, causing the original regex to not match.Steps to Reproduce
my.registry.url:10000/path/to/imagerepoURLIsRegex: "true"andrepoURL: "my.registry.url:10000/.*"repoURL: "my.registry.url.10000/.*"Version
Kargo v1.0.3