[GitHub] [incubator-devlake-helm-chart] JorgeGar commented on pull request #143: feat: use Scarf Gateway for DevLake helm charts downloads

["JorgeGar (via GitHub)" <gi...@apache.org>]

JorgeGar commented on PR #143:
URL: https://github.com/apache/incubator-devlake-helm-chart/pull/143#issuecomment-1628652136

   > @matrixji unfortunately the default endpoint from DockerHub provides poor usage metrics, which hinders the ability of DevLake maintainers to better understand the community makeup and aggregate download trends of the project. Improved observability for DevLake was specifically requested by @hezyin and team. It should be noted as well that this doesn't change the repository from which DevLake is being served - it's just a redirect, so devlake.docker.scarf.sh/apache/devlake will just redirect to registry-1.docker.io/apache/devlake.
   
   Hi @arjundevarajan I have one question about Scarf Gateway if I may. I see the value for DevLake on using it, but I am a bit concerned about companies' policies that may not allow to get images from places outside Docker or maybe AWS registry. AFAIU, Scarf acts as a traffic gateway. Could this be an issue? or is it completely transparent?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org