Re: [VOTE] Release Apache Camel K 1.0.0 and Runtime 1.3.0

2020-06-06 Thread Nicola Ferraro
If you tried it on Minikube, the new image builder doesn't start a new pod to download the maven artifacts. This saves a lot of build time, but requires more memory in the operator pod. Just guessing what can be the cause.. Nicola On Sat, Jun 6, 2020 at 9:28 AM Claus Ibsen wrote: > +1 (binding)

Re: camel-k: switch to Quarkus as default framework for integrations

2020-06-06 Thread Federico Valeri
+1 On Sat, Jun 6, 2020 at 7:57 AM Claus Ibsen wrote: > > +1 > > On Fri, Jun 5, 2020 at 1:45 PM Luca Burgazzoli wrote: > > > > Hello everyone, > > > > When we started working on camel-k, we haven't found any runtime/framework > > that could cope with the type of workloads we had in mind for camel

Re: [VOTE] Release Apache Camel K 1.0.0 and Runtime 1.3.0

2020-06-06 Thread Claus Ibsen
+1 (binding) Tried some of the examples and they work fine. And really love the speedy new image builder. And that I can see the command line that started CamelK in the log (thanks Antonine) However I noticer the operator pod is taking up a fair bit of memory (59MB). I dont reall on top of my hea