kamel run with --name in camel-case converting to kebab-case

I noticed that when I run an integration forcing a name in "camel-case" style, it automatically is renamed to "kebab-case". Here is the shell output: $ kamel run cron.groovy --name aaBbCc Modeline options have been loaded from source files Full command: kamel run cron.groovy --name aaBbCc Integra

Integration resource not created with spec.replicas and unavailable to autoscaling via HPA

I created a simple integration exposing a REST endpoint. This endpoint when invoked consumes a lot of CPU (100%) for testing... I defined the traits: - container.limit-cpu=1000m - container.request-cpu=1000m After that, I created the hpa resource: - kubectl autoscale it my-integration-high-cpu-u

Why rest consumer isn't using HTTPS

definedI created an integration to invoke itself 10 times. https://pastebin.com/7vWwKuXT But when the first request comes to it via e.g. https://my-host/integration/token/xx/invoke/api/loop the second one will be emitted using HTTP instead of HTTPS, even I had defined the "restConfiguration()

Can I scale the Camel-K-Operator deployment?

Can I autoscale the Camel-K-Operator deployment to have more than one pod processing/building/runnning integrations?

Webhook for listening Integration CRD changes

There is a way to create a webhook to listen for Integration CRD changes? I was looking this https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/ But I do know if this is possible I want to be notified when an Integration phase changes to "Running" or "Err

"When" the kubernetes service is exposed/created

At what moment the kubernetes service is exposed/created for an integration that has an REST exposed? I need to discover this service to get the node-port and persist it on my "api gateway" to be able to proxy the requests from my gateway to the correct integration. I was thinking about a "loop"

Re: Integration keeps reconciling build, why?

Claus, sorry. After a while the operator finally built it. On Mon, Mar 21, 2022 at 2:30 PM Claus Ibsen wrote: > > Hi > > Does other integrations build and run without logging this kind of thing? > > > On Mon, Mar 21, 2022 at 3:48 PM Roberto Camelk > wrote: > > >

Can I expose 2 tcp ports in the same integration?

I was reading this doc: https://camel.apache.org/camel-k/1.8.x/traits/service.html About the k8s service creation. It is automatically created and just based on the camel http component, right? Is it possible to create/expose 2 or more tcp/http ports automatically in the k8s service (like using c

Integration keeps reconciling build, why?

I'm testing some integrations. My last test is about trying to expose 2 rest endpoints in 2 different ports (I don't know if it is possible)... But when I run it, the camel-k operator seems to infinite loop trying to build the integration, without giving me "details" about what is realy happening.

Re: Trying to create REST integration

I found the problem. I was running my integration forcing the name with "--name camel-rest", so the source file/class name refactor wasn't solving the issue. Now I renamed both (class and name arg) and it's working. On Thu, Mar 17, 2022 at 12:55 PM Roberto Camelk wrote:

Re: Trying to create REST integration

.java:45) On Thu, Mar 17, 2022 at 11:51 AM Pasquale Congiusti wrote: > > Hello, > try calling your class differently than *CamelRest* (ie, CamelRest2) . I > think it makes some mess because it conflicts with the component name. > > Cheers, > Pasquale. > > On Thu, Mar 17, 2

Trying to create REST integration

I'm trying to run the REST example from here: https://camel.apache.org/manual/rest-dsl.html#_rest_dsl_with_java_dsl This is my final source: //camel-k: dependency=camel-rest import org.apache.camel.builder.RouteBuilder; public class CamelRest extends RouteBuilder { @Override public voi

Re: kamel install --global vs kamel get -n

ed to also look for an operator globally, > > not only within its namespace. > > > > On Thu, Mar 17, 2022 at 5:05 AM Roberto Camelk < > > betonetotbo.cam...@gmail.com> > > wrote: > > > > > I recently installed the camel-k 1.8.2. During the proce

kamel install --global vs kamel get -n

I recently installed the camel-k 1.8.2. During the process I passed the arg --global to enable camel-k-operator to manage all namespaces. Now, when I query the integrations running in a specific namespace via "kamel get -n my-namespace" I got this output: > No IntegrationPlatform resource in my-s

Isolate integrations network

How can I isolate integrations network, for example, to prevent an integration A to request a rest route in the integration B ?

Camel-K integration hot deploy and down time

When an integration is running in my k8s cluster via Camel-K operator, what happens if I re-run it and it will rebuild? There will be downtime? This downtime will be from the beginning of the build phase, or just when it switches the POD to the new image?

Using AWS ECR with Camel-K, is it possible?

Is it possible to use AWS ECR with Camel-K to push the images ?

Kamel CLI exit code

I'm using kamel CLI to launch my integrations programmatically. I was testing the kamel exit code, assuming that 0 (zero) is "everything ok". But recently I have launched an integration containing a invalid Modeline: //camel-k: trait=prometeus.enabled=true The correct is ("h" was missing): //cam

Camel-K integration status phases

What are the values of integration status phases? In the API documentation this field is a "string", so anything is possible ehehehe... Here is an sample about the output of the "get integration" that am I using to map this "status.phase" to a enumeration inside my application: kubectl get integ

Kamel CLI output as JSON

Is it possible to configure kamel CLI to always output as JSON (or yaml) ?

Re: Running integration via k8s API

ent route > definition (ie, cron:xyz), whilst the microprofile is instead defined by > the prometheus trait, so, although you don't define it explicitly, then, > the dependency is added during the application build. > > Regards, > Pasquale. > > On Mon, Dec 20, 2

Running integration via k8s API

I'm launching camel-k integrations via kubernetes API. I just create an "Integration" resource definition in JSON and submit it. Recently I was trying to create integrations with dependencies like "camel:cron" and "camel:microprofile-metrics" but WITHOUT defining them in the "dependencies" field.

Re: CLI vs API: modeline strange behaviors

ds the parameters provided in the Integration into a full command. > > Regards, > > Pasquale. > > > [1] https://camel.apache.org/camel-k/1.7.x/cli/modeline.html > > > On Fri, Dec 17, 2021 at 3:52 PM Roberto Camelk > wrote: > > > The YAML below is a snippet

CLI vs API: modeline strange behaviors

The YAML below is a snippet of my Integration resource in k8s, got by: kubectl get integration -o yaml apiVersion: camel.apache.org/v1 kind: Integration metadata: creationTimestamp: "2021-12-15T11:22:48Z" generation: 1 name: micro-profile-metrics2 namespace: default resourceVersion: "85

Re: Camel-K API client library (io.fabric8)

Andrea Cosentino wrote: > > Hello, > > The project is this one > > https://github.com/fabric8io/kubernetes-client/tree/master/extensions/camel-k > > Il giorno ven 17 dic 2021 alle ore 12:18 Roberto Camelk < > betonetotbo.cam...@gmail.com> ha scritto: &g

Camel-K API client library (io.fabric8)

Does anyone know this library? group: io.fabric8 artifact: camel-k-client version: 5.10.1 I'm facing problems with it in the IntegrationStatus mapped entity. It's mapping a deprecated field "kit" instead of the new one "IntegrationKit" So, I'm trying to find this library repository to report the

Re: Operating Camel-K by rest instead of via CLI kamel

e, Dec 14, 2021 at 3:56 PM Antonin Stefanutti 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/conce

Operating Camel-K by rest instead of via CLI kamel

Can I operate the Camel-K Operator via http instead of via kamel CLI ?

Camel-K build process getting killed

Why sometimes the camel-k build is killed printing this log: {"level":"error","ts":1639135593.228176,"logger":"camel-k.controller.build","msg":"Build kit-c6pjgfbh6q8s73fjjqs0 failed: failure while building project: signal: killed","request-namespace":"default","request-name":"kit-c6pjgfbh6q8s73fj

Re: Camel-k operator fails on building

in the `default` namespace. > > > On 9 Dec 2021, at 20:14, Roberto Camelk > > wrote: > > > > I installed camel-k in my "default" namespace in minikube. This is my > > scripts: > > > > read -p 'Dockerhub organization: ' dockerorg

Camel-k operator fails on building

I installed camel-k in my "default" namespace in minikube. This is my scripts: read -p 'Dockerhub organization: ' dockerorganization read -p 'Dockerhub user name: ' dockeruser read -sp 'Dockerhub user password: ' dockerpassword kubectl \ -n camel \ create secret docker-registry camel-k-regist

Re: Multiple CamelContexts using Camel-K

tworkPolicies, Quotas, whose > definitions are tightly bound to that of namespaces: > > https://kubernetes.io/blog/2021/04/15/three-tenancy-models-for-kubernetes/#namespaces-as-a-service > > On 8 Dec 2021, at 12:25, Roberto Camelk > mailto:betonetotbo.cam...@gmail.com>>

Re: Multiple CamelContexts using Camel-K

Antonin, is it correct assuming that the correct mode to deal with multi-tenancy in k8s is by using namespaces? There is any official documentation about this? On Tue, Dec 7, 2021 at 3:19 PM Antonin Stefanutti wrote: > > > > On 7 Dec 2021, at 18:31, Roberto Camelk > > wro

Re: Multiple CamelContexts using Camel-K

> (think one integration = one Camel context) > > If you really want strict multi-tenancy, it's also possible to have an > operator instance per tenant (= namespace), but that comes with extra > overheads, resources wise and operationally wise. > > > On 7 Dec 2021

Re: Multiple CamelContexts using Camel-K

ost a > single Camel context. > > For monitoring, the metrics exposed are tagged with the context info. > > > On 7 Dec 2021, at 15:15, Roberto Camelk > > wrote: > > > > We are thinking about organizing our infra loading one CamelContext > > per tenant in ou

Multiple CamelContexts using Camel-K

We are thinking about organizing our infra loading one CamelContext per tenant in our cloud. So the idea is one CamelContext per tenant, so each tenant has its own environment and it can not be impacted by other tenant environments (contexts). This makes sence? What are the issues about this abor

Re: Explain camel processing metrics

ep in a route > > > > On Mon, Dec 6, 2021 at 3:28 PM Roberto Camelk > wrote: > > > > This are the list of all camel-k metrics exposed via > > quakus-microprofile-metrics component: > > > > application_camel_context_exchanges_completed_total{camelContext=&

Explain camel processing metrics

This are the list of all camel-k metrics exposed via quakus-microprofile-metrics component: application_camel_context_exchanges_completed_total{camelContext="camel-1"} 1066.0 application_camel_context_exchanges_failed_total{camelContext="camel-1"} 0.0 application_camel_context_exchanges_inflight_c

Re: Better details about microprofile metrics

n Camel is not doing anything currently. > > On Thu, Dec 2, 2021 at 1:42 PM Roberto Camelk > wrote: > > > > I'm trying to understand better what each metric means > > > > But this doc > > https://camel.apache.org/camel-quarkus/2.5.x/reference/

Better details about microprofile metrics

I'm trying to understand better what each metric means But this doc https://camel.apache.org/camel-quarkus/2.5.x/reference/extensions/microprofile-metrics.html#_camel_context_metrics is not cleary enough for me. For example: camel.context.exchanges.inflight.total The total number of infligh

Re: Question about camel metrics IDs

OK, thanks! But it is a little tricky for me... Is there no correlation possibility between the JMX metrics and the Microprofile Metrics at all? A challenge, try adapt this grafana dashboard based on JMX metrics: https://github.com/weimeilin79/camel-k-example-prometheus/blob/master/grafana/Sample

Re: Question about camel metrics IDs

OK, thanks. But, can I setup the JMX exported in a Camel-K integration? On Wed, Dec 1, 2021 at 2:39 PM Antonin Stefanutti wrote: > > > > On 1 Dec 2021, at 18:08, Roberto Camelk > mailto:betonetotbo.cam...@gmail.com>> wrote: > > I found a prometheus yaml conf

Question about camel metrics IDs

I found a prometheus yaml config, who's using some scrape definitions and I need to find the correlated metrics in camel-k. Here are the scrape patterns: https://github.com/alainpham/app-archetypes/blob/1f559e84753525b087a503ecb2d97c26e108dee7/spring-boot-camel/src/main/resources/archetype-resourc

Re: Why my prometheus operator not discovering new camel-k pods

ng fixes the issue, as it forces an > update. > > There may be some configuration parameters to update in the Prometheus > resource. It's strictly related to the Prometheus operator, so you'll have > better answer if you ask the Prometheus operator team directly. > > On

Why my prometheus operator not discovering new camel-k pods

I created a simples integration and enabled the prometheus integration, as explained here: https://camel.apache.org/camel-k/1.4.x/observability/integration.html#_discovery Before that, I also configured my Prometheus operator resource, as explained here: https://camel.apache.org/camel-k/1.7.x/obse

Re: Apache Camel-k metrics in rancher embedded prometheus

values: - p-gzj4v serviceMonitorSelector: {} tolerations: - effect: NoSchedule key: cattle.io/os operator: Equal value: linux version: v2.17.2 volumes: - emptyDir: {} name: nginx-home On Fri, Nov 26, 2021 at 11:41 AM Roberto Camelk wrote: > > Thanks agai

Re: Camel-k and microprofile metrics

ing project: > signal: > killed","request-namespace":"platform","request-name":"kit-c6gi8msurk73bvs3vdu0","api-version":"camel.apache.org/v1","kind":"Build","ns":"platform",&quo

Re: Camel-k and microprofile metrics

quot;:"20","task":"builder"} 26/11/2021 15:41:01 {"level":"info","ts":1637952061.279381,"logger":"camel-k.maven","msg":"executing: mvn --no-transfer-progress -Dstyle.color=never -Dmaven.repo.local=/tmp/ar

Camel-k and microprofile metrics

Hi, I'm trying to create a sample um route using microprofile metrics. So I created this java source file containing: //camel-k: dependency=camel-cron //camel-k: dependency=camel-quarkus-microprofile-metrics public class LoggedInRoute extends RouteBuilder { @Override public void configu

Re: Strange behavior with camel-k and java lang

Okay, no problem! I understand this is a new tool and very promising one! I relieved, confirming the strange behavior, that was not my head trolling me. Thanks for the fast-feedback. On Fri, Nov 26, 2021 at 2:16 PM Luca Burgazzoli wrote: > > On Fri, Nov 26, 2021 at 6:09 PM Roberto

Strange behavior with camel-k and java lang

I recently installed Camel-K for testing purposes. This was my installation command: kamel install \ --force \ --build-publish-strategy=Spectrum \ --olm=false \ -n platform \ --operator-resources requests.cpu=100m \ --operator-resources limits.cpu=200m \ --operator-resources requests

Re: Apache Camel-k metrics in rancher embedded prometheus

; # HELP application_camel_route_exchanges_completed_total The total number of > completed exchanges for a route or Camel Context > # TYPE application_camel_route_exchanges_completed_total counter > application_camel_route_exchanges_completed_total{camelContext="camel-1",routeId=

Re: Apache Camel-k metrics in rancher embedded prometheus

theus-operator/prometheus-operator/tree/v0.52.1/example/user-guides/getting-started > > And the troubleshooting guide at: > > https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/troubleshooting.md > > > > On 26 Nov 2021, at 12:32, Roberto Camelk

Re: Apache Camel-k metrics in rancher embedded prometheus

e Prometheus operator, like the > namespace, the labels, ... > > Some documentation is available at: > > https://camel.apache.org/camel-k/1.7.x/observability/monitoring/integration.html#_discovery > > That contains some links to the Prometheus operator documentation for > trouble

Apache Camel-k metrics in rancher embedded prometheus

I have a Kubernetes running Rancher 2.4.3. I have the cluster monitoring enabled in rancher, so that exists a Prometheus instance running, so as a Prometheus Operator. Recently I deployed a Apache Camel-K operator, and now I want to enable the prometheus integration for collect metrics about my ca