Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Luca Burgazzoli
    @lburgazzoli
    seems an issue with the registry
    can you check if the required images exists ?
    Claus Ibsen
    @davsclaus
    @athishsreeram got that MANIFEST error too once, i restarted minikube and/or also reset kamel k
    one issue i had that caused this was my namespace was memory limited per pod, so the builder pod ran OOME and this caused following builds to still fail, when i lifted the memory limit
    haris-zynka
    @haris-zynka
    Hi, can someone help me with this? I have an issue with using http4. If I run it without dependency it tells me that it cannot find http4 component but if I add camel-http4 as dependency it cannot find it to download. Using with minishift, kamel RC1 and groovy scripts. I need to consume an HTTPS endpoint.
    Andrea Cosentino
    @oscerd
    In camel 3, camel-http4 has been renamed to camel-http
    the scheme is http now
    so you need to use http and if you need the dependency camel-http
    haris-zynka
    @haris-zynka
    ok thx, it makes some issues as it forces me to use bridge to be able to consume from endpoint rather then exposing it
    Andrea Cosentino
    @oscerd
    I don't understand the problem.
    what are you trying to do?
    haris-zynka
    @haris-zynka
    I'm having camel-rest + camel-http. It could be that some parts collide and mess up my intentions but I'm going from REST endpoint, process body, then try to reach second endpoint with the new body
    Bruno
    @BrunoNetId_gitlab
    @haris-zynka please share your code, maybe you're missing to clean the headers (removeHeaders) which might mislead calling the endpoint
    haris-zynka
    @haris-zynka
    @BrunoNetId_gitlab thx I've fixed it already and it was the headers, although I've changed headers in the code by adding .setHeader(Exchange.HTTP_URI, url) instead of using .to("https://url")
    haris-zynka
    @haris-zynka
    so now it looks like .setHeader(Exchange.HTTP_URI, url) .setHeader(Exchange.HTTP_METHOD, constant("GET")).to("https://temp") and it still makes some problem with the special chars, I tried converting to string with utf-8 and then back to json as response but special chars stay weird looking, I don't know is it a postman thing
    Saravanakumar Selvaraj
    @saravanakumar1987
    Hello Community,
    I am working on a proposal to migrate the camel applications in production from 2.17 to 3.1. (Fuse 6.3 to upcoming Fuse version)
    The customer don’t have openshift purchased but already have AWS license. Does Camel-K or Camel-Quarkus work fine in AWS EC2 or EKS? If any case study or an article from the community regarding this, it will be helpful.
    Thank you!
    Matt Brown
    @gowabash
    Cross posted from #apache-camel. I'm doing some research into camel and came across camel-k. This seems like the exact kind of tooling that I am looking for. However I can't even get the samples to run. I've downloaded and installed Camel K Client 1.0.0-RC1. I've donw the intall setup against my local docker-desktop using my dockerhub registry. When I try to run kamel run helloworld.groovy --dev (from the getting started page) it gets to the Building Kit phase but never finishes. When I look into k8s logs at the camel-k-kit-builder container, there is an error message Invalid JSON Patch. I've also tried the java example with the same error. I found an issue on the issue tracker (#1190), but no comments there either. Is there something I'm missing? Is there a better way to get started?
    Matt Brown
    @gowabash
    Since this original posting, I have downloaded M4 and was able to get everything to compile, but it looks like getting them published to the registry is the issue. Some additional logging around early issues might help others in this error. If we decide to go in the route, I'll work on that,
    Matt Brown
    @gowabash
    I was able to get the helloworld.groovy example working with M4. Seems like 1190 is a real defect
    Jonathan-Eid
    @Jonathan-Eid
    Hey guys
    I'm trying to get a spring-ws up on camel-k using camel-spring-ws
    I would like to spin up the example on the camel/examples github
    but I'm so clueless as to how to Camel-K relates to Camel
    What would be a better way to approach getting a Spring Web Service up on Camel-K?
    haris-zynka
    @haris-zynka
    @Jonathan-Eid Not sure about Spring WS but for me it helped to understand Camel K as a build tool so instead of maven or gradle I have an extra layer of build that will convert my files to kubernetes way of doing stuff. Other than that I'm using Groovy and I have only one file per "service" because you can't just import files like you used to. To add extra dependencies I have to do command by adding "-d com.some.depenedency" so I just write everything in one file and have multiple services. I guess you must build your WS same way you need to provide dependencies through kamel (command) somehow. Although I think then you need to configure maven paths for camel K.
    Andrea Tarocchi
    @valdar
    @Jonathan-Eid another good point to start are the examples int he documentation, before starting with a WS try a simpler one and poke around just to understand what are the moving parts. If you don't have a Kubernetes experience a good prima on Kubernetes it is also helpfull
    Jonathan-Eid
    @Jonathan-Eid
    Okay I think I got passed that
    How do I expose a Camel K integration as a nodeport?
    Jonathan-Eid
    @Jonathan-Eid
    Okay I was able to rip the service.yaml of the integration
    edit it to a nodeport and reapply it but the service exists only for the lifetime of the pod\
    Andrea Tarocchi
    @valdar
    I think that the camel-k operator is taking care of cleaning things up if you delete the integration
    @Jonathan-Eid ^^
    Jonathan-Eid
    @Jonathan-Eid
    I lied
    once applying the service
    It stays for the duration of the integration even when the pod goes down :D
    The service only resets when you edit the content of the integration however
    Krzysztof Sobkowiak
    @sobkowiak
    Hi. I'm installing the RC1 on Minikube with knative 0.11.0 using kamel install. After installatiin I can see only the operator pod. The pods for camel-k-java-builder (and the other) are missing. Do
    Am I doing something wrong?
    After starting the integration e.g. kamel run Sample. java it takes very long time until the integration is built first time
    Krzysztof Sobkowiak
    @sobkowiak
    Looking at the logs for the builder pid I can see logs from kaniko trying to download the image for the builder but it fails to download it from the cache. This part of the build takes the most time
    Installing kamel with option --kit java the pod camel-k-java-builder is created. After starting the integration a new builder pid is created. It tries to download the image for camel-k-java but again it takes a long time and fails with the kaniko cache.
    Krzysztof Sobkowiak
    @sobkowiak
    In both cases the integration is finally built but it takes a long time
    Nicola Ferraro
    @nicolaferraro
    Hi @sobkowiak this is a known issue. Kaniko performances degraded over time and we decided to add an alternative in RC2 (buildah). Typical build times are ~1 minute in RC2 and we have a plan to possibly reduce them to ~30secs in the 1.0.0 release. RC2 release is planned for the end of next week, but you try it building from master if you want
    Krzysztof Sobkowiak
    @sobkowiak
    Thanks @nicolaferraro for the info. It's a good news about the change to buildah. I'm on vacation from tomorrow, so I'll try the new release at the end of the week.
    I have a talk about Apache Camel and Camel-K in a conference in Wroclaw in 4 weeks. Do you have any interesting slides I could use as idea for my talk?
    Nicola Ferraro
    @nicolaferraro
    That's great @sobkowiak !
    I've ended my "conference cycle" at the end of last year and will start again at the end of March, with a new slide deck.. but today I can give you only the last ones that I've used at DevNation London in October..
    If gitter does not crash..
    Nicola Ferraro
    @nicolaferraro
    DevNation London - Cloud Native Integration with Camel K (1).pdf
    Krzysztof Sobkowiak
    @sobkowiak
    Thanks a lot @nicolaferraro for the slides!