Hi, I'll try to answer inline. Il giorno ven 7 mag 2021 alle ore 01:36 Gerald Kallas <catsh...@mailbox.org.invalid> ha scritto:
> Dear Camel-K folks, > > we're currently evaluating Camel-K for a new integration platform of a > fashion retailer. At first, many thanks for all your effort of designing > and developing the Camel-K platform! > > With the current version 1.4 we've some questions for those I wasn't able > to find all the answers on the Camel-K website and on other sources. I've > researched a lot for all those details. > > I'm curious whether the current architecture is still valid shown here > https://camel.apache.org/camel-k/latest/architecture/architecture.html > (referenced to version 1.1.1). If not, do you have a newer architecture and > maybe also in any case some explanations to the building blocks within the > architecture? > That has not changed. There are some changes needed wrt Kamelets, but the core is still the same. > Further we want to run integrations real "serverless". What do you > recommend in this case? Pre-compile based on GraalVM to small binary? How > looks like the recommended approach from development over test to > production? > > Some further questions we got from our client .. > * For a common deployment of an integration, will there be created an > image including a JVM every time? > Yes, for now. We do create JVM based images now, the promise is to do native mode in one of the next releases: https://github.com/apache/camel-k/issues/991. It's been postponed since it's a hard task, but that's one of the reasons why we switched to Camel-quarkus as sole runtime, so definitely a main goal. > * What are the requirements to build the image locally (not on the > cluster)? > This is a new feature added (to build images using "kamel local build"), but the images are meant to be run locally, we're not testing the full workflow in CI (i.e. reusing the same images on the cluster). We'll appreciate feedback on that. Building locally requires docker and java JDK 11 locally. > * What connections are possible to deliver runtime events to Grafana and > Prometheus? > Any integration can send metrics to Prometheus via the prometheus trait. Additionally you can also configure your own custom metrics and inject them in the integrations. Grafana talks to prometheus then. > * What are the recommendations to perform debugging and later on unit > tests? > We've added a "kamel debug command" to do debugging on running code in a remote cluster. There's also a "kamel local run" that usually helps doing troubleshooting without having to connect to a cluster. Unit tests can be added to the libraries of code you use in the integration routes, while for the full integrations you can use YAKS to do e2e tests. > A lot of questions but I would be more than happy if one could make the > details more clear for us. > > Many thanks in advance. > Best - Gerald
