> On 14 Dec 2021, at 20:29, Roberto Camelk <[email protected]> wrote:
> 
> Sorry, maybe I wasn't clear enough in my question, or I simple didn't
> understud your answer.

No problem, that's me that did not understand your use case :)

> What I'm thinking about is how can I create a web-ui to launch my
> integrations by just submitting a source file of it?
> 
> I want to publish a backend to be able to send requests containing the
> integration source, and this backend orchestrates the "kamel run" for
> me. So as to orchestrate the "kamel get" and "kamel delete" for
> example...
> 
> I was thinking if it is possible that the Camel-K has an REST API to
> do that for me, or if I need to create this.

It's possible to create Integration resources directly, using the Kubernetes 
API, as any other Kubernetes resources.
That is what GUI clients typically use.

Ultimately, the kamel CLI is just a wrapper, that creates an Integration 
resource using the Kubernetes API.
You can see what the Integration looks like by running:

$ kamel run your_integration_file -o yaml

> On Tue, Dec 14, 2021 at 3:56 PM Antonin Stefanutti
> <[email protected]> wrote:
>> 
>> The Camel K operator is a standard Kubernetes Deployment, which is typically 
>> "operated" using the kubectl CLI, but can also be operated using the 
>> Kubernetes HTTP API:
>> 
>> https://kubernetes.io/docs/concepts/overview/kubernetes-api/
>> 
>> On 14 Dec 2021, at 19:36, Roberto Camelk 
>> <[email protected]<mailto:[email protected]>> wrote:
>> 
>> Can I operate the Camel-K Operator via http instead of via kamel CLI ?
>> 

Reply via email to