Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flux image reflector is not able to use Jfrog artifactroy #421

Open
gabbler97 opened this issue Jul 17, 2023 · 1 comment
Open

Flux image reflector is not able to use Jfrog artifactroy #421

gabbler97 opened this issue Jul 17, 2023 · 1 comment

Comments

@gabbler97
Copy link

We discovered the following issue when we used the Flux image reflector controller with JFrog Artifactory:

The image controller tries to list the tags using this URL:

https://my.artifactory.com/v2/artifactory/path_to_the_tags/subpath_to_the_tags/tags/list?n=1000

It is caused because of the design of the Flux and JFrog Artifactory together:

https://github.com/fluxcd/image-reflector-controller/blob/cc43c0a2909758bb27b18a9343da98214d9dc872/internal/test/registry.go#L116

Instead of this the following URL is reachable and has the same functionality:
https://my.artifactory.com/artifactory/api/docker/path_to_the_tags/v2/subpath_to_the_tags/tags/list


The JFrog has not implemented this API endpoint as the public image repositories.

Here we found a possible workaround.

https://help.octopus.com/t/connecting-an-external-docker-registry-feed-to-artifactory/24825

Do you have any other idea how to solve this?

We do not want to build a custom proxy each time the image reflector is used by different teams.

Thank you in advance!

@GevatterGaul
Copy link

Same issue here :-(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants