apache/camel-k

Chat moved to Zulip -> https://camel.zulipchat.com/

Ari Salonen

@arsalone_twitter

Is there a list of features what are included in Camel(SpringBoot) but not in Camel-K? As I have understood Camel-K is not a replacement for Camel ...

Claus Ibsen

@davsclaus

@arsalone_twitter you cannot compare them 1:1 like that.

its more camel on spring boot vs camel on quarkus you can compare

5 replies

Zoran Regvart

@zregvart

👋 can someone have a look at a broken link in the Camel K docs, the website isn’t getting published: https://builds.apache.org/view/C/view/Apache%20Camel/job/Camel.website/job/master/329/console

Andrea Cosentino

@oscerd

@zregvart should be fixed now, I'm running the website build again

Spencer Clark

@spenceclark_gitlab

I'm trying to run kamel on a managed kubernetes cluster with DigitalOcean.

I've setup a namespace for it, and created the registry secret I need to access our container registry (GitLab)

I install kamel using:

kamel install --registry registry.gitlab.com/xxxx/yyyy --registry-secret gitlab-reg --namespace camel

Everything seems to startup. So I then run a standard "Hello World" example:

kamel run Test-Groovy.groovy --namespace camel

It then shows as "building" when I run "kamel get", and in Kubernetes I can see a new pod start up, but the pod continually fails and restarts.

In the logs for the camel-k-operator pods, I see this error:

Error during unshare(CLONE_NEWUSER): Operation not permitted
User namespaces are not enabled in /proc/sys/kernel/unprivileged_userns_clone.
level=error msg="error parsing PID \"\": strconv.Atoi: parsing \"\": invalid syntax"
level=error msg="(unable to determine exit status)"

I can't see any steps I've missed around permissions so I'm unsure where to go next.

3 replies

Spencer Clark

@spenceclark_gitlab

Sorry, that log error is from the kit builder pod not the operator pod.

coricko

@coricko

Does anyone have a good example of using subclasses when working with rest? I keep getting jackson type conversion errors or camel invalidPayloadExceptions

Luca Burgazzoli

@lburgazzoli

@coricko can you share an example

coricko

@coricko

Is there a way to include a classifier when including a dependency?

Luca Burgazzoli

@lburgazzoli

the dependencies are supposed to be in the following format mvn:<groupId>:<artifactId>[:<packagingType>[:<classifier>]]:(<version>|'?')

Gheorghe-Teodor Bercea

@doru1004

I'm adding some debug statements in kamel source, building the image, pushing it to my docker then I uninstall kamel and install it again in my cluster and I'm still not seeing my log messages when invoking kamel run. Is there another step I'm missing?

Gheorghe-Teodor Bercea

@doru1004

When re-running an integration I want to re-run everything fresh with no reuse from previously running this integration i.e. I want the code to go through all the steps to construct the integration every single time. What do I need to delete/change to get that effect?

Or maybe all my debug messages get redirected and they're just not printed even though I run with --dev ? I'm not sure what's going on

Nicola Ferraro

@nicolaferraro

Hi @doru1004 , that's the expected behavior, every run does not use stuff from previous runs. May you want to share the example, so we can check what's going on? If you delete the whole integration and deploy it afresh, does it work? Sometimes it happened also to me that container logs are not printed when the cluster is overloaded.. but it depends

Gheorghe-Teodor Bercea

@doru1004

I had the impression that certain parts of the code aren't being run such as the dependency aggregation. I have a simple integration just an integration which prints a message to Slack using the Camel Slack component. The very first time I ran it a while back it took a longer to launch then it launched really quickly from then on so it feels like some steps are skipped or cached.

Maybe I'm not deleting the integration ?

Gheorghe-Teodor Bercea

@doru1004

Just to clarify, I'm not seeing the prints I'm doing from within the camel k source code which I'm building myself.

Luca Burgazzoli

@lburgazzoli

you mean the camel k operator ?

Gheorghe-Teodor Bercea

@doru1004

I guess so

When I do a kamel uninstall and then an install again, is there any reuse happening ?

It always seems like the second install is faster than the first, if so is there some cache I need to clear?

Gheorghe-Teodor Bercea

@doru1004

Also when I do kamel run on an integration I'd like the builder to run every time for debug purposes, not sure what I need to modify to get that effect

Luca Burgazzoli

@lburgazzoli

if you are changing the go code, then you need to build a container image, push to a registry and reference it upon install

Gheorghe-Teodor Bercea

@doru1004

I'm doing that

Luca Burgazzoli

@lburgazzoli

so delete the kits

and the builder will kick in

Gheorghe-Teodor Bercea

@doru1004

how do I clear the kits?

Luca Burgazzoli

@lburgazzoli

kamel delete kit

or with kubectl

Gheorghe-Teodor Bercea

@doru1004

is there an additional option I need to pass kamel install with the new image path? I only do this: kamel install --registry=registry:5000 --registry-insecure

Gheorghe-Teodor Bercea

@doru1004

$ k get pods
NAME READY STATUS RESTARTS AGE
camel-k-kit-bs49lrom5h99pjsjpdig-builder 0/1 Completed 0 14d
camel-k-operator-68c8fcf59b-fll45 1/1 Running 0 34m

That's all I have

This is what is outputted when I run kamel run:

integration "sink" created
Condition "IntegrationPlatformAvailable" is "True" for Integration sink: camel-k
Progress: integration "sink" in phase Initialization
Integration sink in phase "Initialization"
Progress: integration "sink" in phase Building Kit
Integration sink in phase "Building Kit"
Condition "IntegrationKitAvailable" is "False" for Integration sink: creating a new integration kit
Progress: integration "sink" in phase Deploying
Condition "IntegrationKitAvailable" is "True" for Integration sink: kit-bs49lrom5h99pjsjpdig
Integration sink in phase "Deploying"
Progress: integration "sink" in phase Running
Condition "DeploymentAvailable" is "True" for Integration sink: deployment name is sink
Condition "CronJobAvailable" is "False" for Integration sink: different controller strategy used (deployment)
Condition "ServiceAvailable" is "False" for Integration sink: no http service required
Condition "ExposureAvailable" is "False" for Integration sink: no host or service defined

Integration sink in phase "Running"
Condition "Ready" is "False" for Integration sink
Condition "Ready" is "True" for Integration sink

Then it just runs and no builder gets invoked

Luca Burgazzoli

@lburgazzoli

if it runs without build it means a compatible kit is still there

kubectl delete ik —all

Gheorghe-Teodor Bercea

@doru1004

That worked

Nice, I can even see it now inside the local registry if I use k get ik

Thanks a lot!

Gheorghe-Teodor Bercea

@doru1004

Is there an additional parameter I need to give kamel install to force it to pull the image from docker or does it do that by default ?

Gheorghe-Teodor Bercea

@doru1004

I changed the builder go code and I want to print some debug messages, where are those messages printed? I use fmt with os.Stdout and I also used log.info () but I can't find where those output messages get printed

Luca Burgazzoli

@lburgazzoli

you can run the operator outside the cluster

6 replies

so scale the deployment

set the env var WATCH_NAMESPACE to the namespace

and run

kamel operator

Where communities thrive

People

Repo info

Activity