davesargrad edited a comment on issue #1059: camel-k installation struggles URL: https://github.com/apache/camel-k/issues/1059#issuecomment-555887423 > You could try to work around the issue by disabling the Kaniko build cache. E.g: > > ``` > apiVersion: camel.apache.org/v1alpha1 > kind: IntegrationPlatform > metadata: > labels: > app: camel-k > name: camel-k > spec: > build: > kanikoBuildCache: false > ``` Hi @jamesnetherton Thanks for this suggestion. I will review the integrationplatform spec that I used this morning, and update it as you suggest (ensure that kanikoBuildCache is false). The instructions I've followed are [these](https://operatorhub.io/operator/camel-k/alpha/camel-k-operator.v1.0.0-m4). The following indicates that the kanikoBuildCache is not explicitly part of the operator.io install instructions. I will try adding it, and recreating the integrationplatform on k8s  > > Or if using the `kamel` binary: > > ``` > kamel install --kaniko-build-cache=false > ``` Per the suggestion of @davsclaus I'm not using the kamel binary, I'm using the instructions on operator.io. I could possibly use the kamel binary instead. However I dont know what to set its various arguments to. The instructions found on the camel-k [documentation page](https://camel.apache.org/camel-k/latest/installation/installation.html) seem to apply to 4 different k8s environments (e.g. openshift, minishift, gke, minikube), that I dont have. What I have is a simple k8s installation on centos-7. From what @davsclaus says, its seems like the operator is the way to go. Looking at operator.io i do think it seems that the camel-k team is using operators as they move towards a full production release of camel-k. Currently it seems to be in alpha, and I'm guessing thats why I'm having the problems I am having. Though I do think that if I can get past this issue it will help them to harden their operator. ---------- Anyways I will try this again and see if disabling that cache helps. @nicolaferraro I'd also try anything that the team suggests, since I'd like to see the team harden camel-k as you drive towards beta
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services
