-
Notifications
You must be signed in to change notification settings - Fork 350
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
Cannot push kit image to GCR (or Docker.io) during integration creation #1024
Comments
Solved by following the procedure outlined on "Installation on GKE" (naming the JSON credentials "kaniko-secret.json" did the trick). The whole procedure does not seem to allow other container registries to be added. |
Right, there's an issue (#613) to allow pushing to other registries. We should add support for them in one of next releases and maybe simplify the process by doing something automatically in the You're welcome if you've time to contribute ;) |
Hi @nicolaferraro, I am not exactly shy when contributing back to open source projects (started with Apache Cocoon waaay back), but my current level of knowledge in Go, Kubernetes, and Camel is pretty low and does not allow any meaningful contribution as a developer. Having said that, I am trying to be un upstanding user by providing feedback. |
Yeah, I know that contributing directly on code is pretty hard in this project.. In any case, we appreciate your feedback! That feature will land for sure in one of next release ;) |
Despite being able to push to both registries and having added a "kanuko-secret" secret with GCR auth, creating an integration fails, with the kit lamenting (on
1.0.0-M4-SNAPSHOT
):The kit describe yilds:
The text was updated successfully, but these errors were encountered: