Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ari Salonen
    @arsalone_twitter
    What should be Camel-K pod memory consumption after native build? I just noted that it is like 100M even there is nothing else than logging
    Claus Ibsen
    @davsclaus
    you need to set resource limits on the pods
    so for native you can lower that to 20-30 etc
    its a bit more heavy in java 11 and latest graalvm than it was with java 8
    there is a trait you can use to set those limits via kamel
    imasood90
    @imasood90
    hi i have question
    with default builder we can are not able to configure apache Camel k with the local repository
    we were successfull to configure it using kaniko
    but getting push error
    but kaniko keeo on using https protocol rathher then http
    is there anyway to conifgure kaniko to use insecure protocal to push image
    imasood90
    @imasood90
    Is there any way to provide kaniko arugument in camel K
    KimJohn Quinn
    @kjq
    Quick question, can k-camel run a spring-boot app (non quarkus)?
    Luca Burgazzoli
    @lburgazzoli
    no, there was support in the early days but the fat jar approach does not play very well with the general goal of camel-k
    coricko
    @coricko
    Is there a way to do less recoveries if the integration fails for some reason? I'm having to wait several minutes with each recovery before it will finally fail in such a way that I can look at the underlying cause
    Claus Ibsen
    @davsclaus
    what recovery can you be more specifc
    coricko
    @coricko
    I'm trying to test https://developers.redhat.com/blog/2019/04/25/build-and-deploy-an-api-with-camel-k-on-red-hat-openshift/ on my local docker-for-desktop. I'm watching the kamel run fail and go through two recoveries before I can finally do a kubectl logs camel-k-kit-brt2kkf89ag8tugjbqn0-builder -c buildah and see that it's due to that image pull issue. My problem is that I spent 5+ minutes waiting for the pod to error so I could look at it and see what happened. Is there a way to set it to only do one recovery before failing?
    Claus Ibsen
    @davsclaus
    kubectl get builds
    should show the in progress builds too
    you can then describe a build
    and btw what version of camel k do you use
    coricko
    @coricko
    image.png
    I'm using kamel version 1.0.0 on windows.
    coricko
    @coricko

    Are the camel-k builder pods incompatible with knative when istio injection is turned on for the namespace? I did the following and I am not having any luck until I try the Spectrum build strategy

    1) Reset my docker-for-desktop cluster (Kubernetes version 1.16.5 if it matters)
    2) Install knative-serving version 1.14 with istio-injection
    3) Run kubectl label namespace default istio-injection=enabled
    4) Run kamel install using the github registry
    5) Run kamel run --dev --name customers --dependency camel-undertow --property camel.rest.port=8080 --open-api customer-api.json customer-api.xml from the redhat example above.

    5 replies
    Gheorghe-Teodor Bercea
    @doru1004
    Has anyone tried to bind to registry a local bean? I'm running into a java.lang.ClassNotFoundException when configuring the routes: "[1] Caused by: java.lang.ClassNotFoundException: MyProcessor
    [1] at org.apache.camel.impl.engine.DefaultClassResolver.resolveMandatoryClass(DefaultClassResolver.java:87)
    [1] at org.apache.camel.support.PropertyBindingSupport.resolveBean(PropertyBindingSupport.java:1031)
    [1] at org.apache.camel.main.BaseMainSupport.bindBeansToRegistry(BaseMainSupport.java:928)
    [1] at org.apache.camel.main.BaseMainSupport.doConfigureCamelContextFromMainConfiguration(BaseMainSupport.java:738)
    [1] at org.apache.camel.main.BaseMainSupport.autoconfigure(BaseMainSupport.java:507)
    [1] at org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:570)
    [1] at org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:379)
    [1] at org.apache.camel.k.main.ApplicationRuntime$MainAdapter.doInit(ApplicationRuntime.java:197)
    [1] at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
    [1] ... 3 more" I have already specified MyProcessor as a property to kamel CLI: "kamel run --property camel.beans.myProcessor=#class:MyProcessor"
    1 reply
    Gheorghe-Teodor Bercea
    @doru1004
    Unrelated to the previous question, when I add a dependency on a GitHub repo using "-d github:user/repo" how can I control the version of the project that is being used? Can I pass a commit ID ?
    1 reply
    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