You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2019/11/21 08:30:46 UTC

[GitHub] [camel-k] nicolaferraro commented on issue #1059: camel-k installation struggles

nicolaferraro commented on issue #1059: camel-k installation struggles
URL: https://github.com/apache/camel-k/issues/1059#issuecomment-556975636
 
 
   Hi @davesargrad, we should make sure we print a more informative error and not proceed with making the integrationplatform ready if there are not the right conditions.
   
   I see you're not declaring any target docker repository in the IntegrationPlatform. Camel K needs to produce the container images for you and push them somewhere in order to create the deployment later.
   
   On minikube there's a unauthenticated registry that is configured automatically by the kamel CLI or you can provide the configuration in the integrationplatform. On minishift and openshift there's always an internal registry that we use by default. The only public (authenticated) registry that we support is gcr.io and instructions to configure it are provided in the link I've sent.
   
   There's an issue open for working with any docker registry and we plan to fix it for 1.0.0-M5 (#613).

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services