Hi The Kamel CLI saves the integration file as a k8s crd. Where the groovy code is embedded inside the crd.
The operator watches for CRDs and then act upon when they are added/deleted/modified. And in case of the embedded Camel code, the operator then "figures out how to build that" and run it. On Mon, Sep 12, 2022 at 4:45 PM Christoph Weiss <christoph.we...@de.ibm.com> wrote: > Hi Claus, > > Thanks for the quick response. I am already quite familiar with the > provided page - and the basic concepts. > > However, I am missing details how a given integration written in a > specific DSL - e.g. groovy - is transformed into a Kubernetes CR object. > Is this something done by the "kamel CLI locally" or is it done on the > cluster via the Camel-K Operator? > > Any insights are more than welcome > > Thanks Christoph > > > > -----Original Message----- > From: Claus Ibsen <claus.ib...@gmail.com> > Sent: Monday, 12 September 2022 16:28 > To: users@camel.apache.org > Subject: [EXTERNAL] Re: kamel run - which component creates the Kubernetes > CR ? > > Hi > > See the Camel K architecture documentation that helps clear up some of > your questions > https://camel.apache.org/camel-k/1.10.x/architecture/architecture.html > > On Mon, Sep 12, 2022 at 4:21 PM Christoph Weiss < > christoph.we...@de.ibm.com> > wrote: > > > Hello, > > > > Short question: I am wondering which “component” is creating the > > “Kubernetes Integration CR” when running “kamel run” (based on a given > > Integration written e.g. in groovy or any other DSL). > > Is this done locally by the CLI tool – or already a function happing > > on the Cluster / Operator site? > > Any information / insights are appreciated. > > > > Thanks for your help in advance! > > > > Christoph > > > > > > -- > Claus Ibsen > ----------------- > http://davsclaus.com @davsclaus > Camel in Action 2: https://www.manning.com/ibsen2 > -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
