[Deployment] Interaction with the Cluster

[Delawen]

We want the user to be able to interact with the cluster with the following features:

• List available integrations already running in the cluster
• [Java] Create endpoint to stream log of integration #55
• Deploy an integration created on the editor
• Stop an existing running integration.
• Cluster #19
• Cluster integration and deployment from the UI kaoto-ui#192

All these leveraged through Camel-K to simplify the implementation.

[Delawen]

Some information:

Camel K runs on Kubernetes using CRDs as APIs: https://camel.apache.org/camel-k/next/apis/camel.html

We can use a similar approach as to what YAKS do, maybe even reuse their model?: https://github.com/citrusframework/yaks/tree/main/java/steps/yaks-camel-k/src/main/java/org/citrusframework/yaks/camelk/model

YAKS uses the Fabric8io extension for Camel K: https://github.com/fabric8io/kubernetes-client/tree/master/extensions/camel-k like this: https://github.com/citrusframework/yaks/blob/main/java/steps/yaks-camel-k/src/main/java/org/citrusframework/yaks/camelk/actions/kamelet/CreateKameletAction.java#L132

[Delawen]

Renaming the deployment API endpoint too. Makes more sense to have the semantics of a REST API with integrations.