tadayosi edited a comment on pull request #2246: URL: https://github.com/apache/camel-k/pull/2246#issuecomment-904314320
This pull req is left with no reviews, besides it has conflicts now. I still don't see why it's necessary yet. Does it mean Camel K doesn't work with ECR, and have bad implications with Quay? If it has some problems with ECR and Quay registries, it's better to first file an gh issue to explain the case. One workaround I can think of is to use an internal registry https://hub.docker.com/_/registry instead for the build kits. -- 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-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
