by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Ben Buzzelli
    @benbuzz68_twitter
    I added the transform because I thought it needed to be in json format. I believe I have it as a string
    Andrea Cosentino
    @oscerd
    Maybe create a little reproducer on github.
    Jason Carreira
    @jasoncarreira

    I'm trying to get it running on AKS and running the simple hello world groovy is crashing: ```
    NAME READY STATUS RESTARTS AGE
    camel-k-cache 0/1 Completed 0 87s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 ContainerCreating 0 11s
    camel-k-operator-ff59498b6-bpqhz 1/1 Running 0 10m

    camel-k-ctx-br2nikjk24uknhitbh4g-builder 1/1 Running 0 69s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 1/1 Terminating 0 70s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Terminating 0 71s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Terminating 0 72s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Terminating 0 72s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Pending 0 0s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Pending 0 0s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 ContainerCreating 0 1s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 1/1 Running 0 14s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Error 0 15s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Terminating 0 19s
    camel-k-ctx-br2nikjk24uknhitbh4g-builder 0/1 Terminating 0 19s
    ```

    kubectl logs camel-k-ctx-br2nikjk24uknhitbh4g-builder --follow
    {"level":"info","ts":1590000184.8375664,"logger":"camel-k.builder","msg":"Go Version: go1.12.2"}
    {"level":"info","ts":1590000184.8377185,"logger":"camel-k.builder","msg":"Go OS/Arch: linux/amd64"}
    {"level":"info","ts":1590000184.8378117,"logger":"camel-k.builder","msg":"Camel K Version: 0.3.4"}
    {"level":"error","ts":1590000186.0092275,"logger":"camel-k","msg":"Unexpected error while creating a temporary dir","error":"mkdir /workspace/builder-211368038: permission denied","stacktrace":"github.com/go-logr/zapr.(zapLogger).Error\n\t/home/nferraro/gopaths/camel-k/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/apache/camel-k/pkg/util/log.Logger.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:70\ngithub.com/apache/camel-k/pkg/util/log.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:191\ngithub.com/apache/camel-k/pkg/builder.(defaultBuilder).Build\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/builder/builder.go:66\nmain.main\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/cmd/builder/main.go:80\nruntime.main\n\t/opt/go-1.12.2/src/runtime/proc.go:200"}
    Pallab Banerjee
    @pallab123ban
    Do we have a guide for setting up Camel K on AKS cluster?
    7 replies
    Ben Buzzelli
    @benbuzz68_twitter
    Anyone know how to run Camel K on a kubernetes cluster without openshift? We're using kubernetes with rancher
    Andrea Tarocchi
    @valdar
    it should be possible, there was another guy on this chat who was able to run it on rancher
    @benbuzz68_twitter start by folowing the intsll camel-k on k8s strategy
    the key part is that you need a registry and a way to build images
    Ben Buzzelli
    @benbuzz68_twitter
    Thanks @valdar !
    Saravanakumar Selvaraj
    @saravanakumar1987

    Hi Community,

    I am able to run a hello world camel K application in openshift using Java DSL. Are there any camel K example in XML or Groovy DSL? Please help!

    Nicola Ferraro
    @nicolaferraro
    Hi, you can run kamel init routes.xml or kamel init myintegration.groovy to create some initial scaffolding with a timer to log. There are also some (unfortunately, non-organized) examples in https://github.com/apache/camel-k/tree/master/examples
    @saravanakumar1987 ^
    Saravanakumar Selvaraj
    @saravanakumar1987

    I see a camel route hello.xml in this examples and is a spring DSL only. But the camel K document says “Spring XML or Blueprint not supported” which may be misleading. However I will try deploying this as suggested.

    I am preparing a proposal for a new integration project using camel-k and quarkus. It deals with a very large number of data, therefore spring boot might be costlier to use. Trying to create a working POC for that.

    Jason Carreira
    @jasoncarreira
    Is there any writeup of what Camel-K is expecting in the secret referenced in "Configuring Registry": https://camel.apache.org/camel-k/latest/installation/registry/registry.html
    Nicola Ferraro
    @nicolaferraro
    @saravanakumar1987 the references to spring are probably just xml namespaces that we've used historically, but there's no spring or spring-boot in the camel k implementation, it's just camel
    @jasoncarreira that should be a Kubernetes "docker credential secret". It can be created also with kubectl.. there's something explained here: https://camel.apache.org/camel-k/latest/installation/registry/dockerhub.html
    Jason Carreira
    @jasoncarreira
    @nicolaferraro Any way to set the secret name via the helm chart? I don't see it as a param, but that would be nice to have
    Ben Buzzelli
    @benbuzz68_twitter
    Has anyone ever used helm to install camel onto kubernetes?

    I see my camel-k-operator pod running, however, when I try to run my camel component,
    my operator logs show this error...

    error looking up service account camel-caravan/camel-k-builder

    Jason Carreira
    @jasoncarreira
    @nicolaferraro Thanks for that... I got the image pull secret set up, and referenced it from my kamel install. Does it need to be in the same namespace? My secret is in the default namespace, but I put Camel-k in a kamel namespace.
    I'm still getting this error, though:
    {"level":"info","ts":1590697575.8871565,"logger":"camel-k.builder","msg":"Go Version: go1.12.2"}
    {"level":"info","ts":1590697575.887198,"logger":"camel-k.builder","msg":"Go OS/Arch: linux/amd64"}
    {"level":"info","ts":1590697575.8872066,"logger":"camel-k.builder","msg":"Camel K Version: 0.3.4"}
    {"level":"error","ts":1590697579.0673268,"logger":"camel-k","msg":"Unexpected error while creating a temporary dir","error":"mkdir /workspace/builder-155296870: permission denied","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\t/home/nferraro/gopaths/camel-k/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/apache/camel-k/pkg/util/log.Logger.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:70\ngithub.com/apache/camel-k/pkg/util/log.Error\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/util/log/log.go:191\ngithub.com/apache/camel-k/pkg/builder.(*defaultBuilder).Build\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/pkg/builder/builder.go:66\nmain.main\n\t/home/nferraro/gopaths/camel-k/src/github.com/apache/camel-k/cmd/builder/main.go:80\nruntime.main\n\t/opt/go-1.12.2/src/runtime/proc.go:200"}
    Claus Ibsen
    @davsclaus
    @saravanakumar1987 @nicolaferraro ah about the spring xml not supported - i have updated the description
    btw i wonder if we should still regard groovy, kotlin and javascript as experimental?
    maybe groovy and kotlin are no longer
    javascript is a bit more unsure as its js engine are dropped from JDK and what else maybe to use in the future and how it would work with graalvm etc
    but to be consistent i marked them as experimental as that is what we say on the camel k readme
    @lburgazzoli @nicolaferraro ^^^^
    @jasoncarreira yeah it would be my understanding that secrets/configmaps are taking from the same namespace where your run the integration - not sure actually if you can refer to it via another namespace. Maybe @nicolaferraro knows?
    also your camel-k is a bit old
    the latest nightly is close to the 1.0 GA
    Nicola Ferraro
    @nicolaferraro
    it must be in the same ns
    Luca Burgazzoli
    @lburgazzoli
    @davsclaus groovy and kotlin are fairly stable but I do agree about marking js as experimental
    Ben Buzzelli
    @benbuzz68_twitter

    @nicolaferraro Sorry, I realized you're in this chat room haha. I emailed you yesterday about an issue I had and you suggested setting the build strategy to Kaniko. Unfortunately that didn't work. I'm still getting this when I run helloworld.groovy... error looking up service account camel-caravan/camel-k-builder

    My guess is that maybe something with my registry is not configured right. I am running it on kubernetes and I also have the rancher console set up with our kubernetes.

    Are there permissions I need to configure for my namespace maybe?

    4 replies
    Jason Carreira
    @jasoncarreira
    @davsclaus is the homebrew kamel install not being maintained?
    Nicola Ferraro
    @nicolaferraro
    @jasoncarreira we've added the homebrew support recently but I've noticed that the version that has been reported is old.. Since we're about to release 1.0.0, we'll update it after that
    Jason Carreira
    @jasoncarreira
    ok
    Jason Carreira
    @jasoncarreira
    Updated to the latest Kamel and tried installing on my Azure AKS:
    Error: cannot check CRD installation after 25 seconds
    1 reply
    Saravanakumar Selvaraj
    @saravanakumar1987

    @saravanakumar1987 @nicolaferraro ah about the spring xml not supported - i have updated the description

    Its perfect now! I am going to try a lot of components this week with and without quarkus.enabled=true.

    Ioannis Polyzos
    @ipolyzos
    @jasoncarreira @nicolaferraro regarding the homebrew version, the homebrew project accept only stable version so the latest version commited is 0.3.4 the-RC, -M etc are not accepted
    Ioannis Polyzos
    @ipolyzos
    Nicola Ferraro
    @nicolaferraro
    Thanks @ipolyzos for clarifying
    @jasoncarreira the error seems similar to what happens on Minishift. Have you tried the helm installer?
    Martin Nigbur
    @anerathil

    Hey guys.
    As i re-deployed out current setup on a blank K8s today, i recognized that the route-integration pods are failing:

    2020-06-05 12:16:54.782 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.ContextConfigurer@623e088f
    2020-06-05 12:16:54.787 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.RoutesConfigurer@6b8d96d9
    2020-06-05 12:16:54.788 INFO  [main] ApplicationRuntime - Add listener: org.apache.camel.k.listener.PropertiesConfigurer@436bc36
    2020-06-05 12:16:54.811 INFO  [main] RuntimeSupport - Looking up loader for language: java
    2020-06-05 12:16:54.815 INFO  [main] RuntimeSupport - Found loader org.apache.camel.k.loader.java.JavaSourceLoader@18920cc for language java from service definition
    Exception in thread "main" java.lang.NoSuchMethodError: 'void org.apache.camel.main.MainConfigurationProperties.addRoutesBuilder(org.apache.camel.RoutesBuilder)'
            at org.apache.camel.k.main.ApplicationRuntime.addRoutes(ApplicationRuntime.java:80)
            at java.base/java.util.Optional.ifPresent(Optional.java:183)
            at org.apache.camel.k.listener.RoutesConfigurer.load(RoutesConfigurer.java:99)
            at org.apache.camel.k.listener.RoutesConfigurer.load(RoutesConfigurer.java:63)
            at org.apache.camel.k.listener.RoutesConfigurer.accept(RoutesConfigurer.java:53)
            at org.apache.camel.k.listener.AbstractPhaseListener.accept(AbstractPhaseListener.java:32)
            at org.apache.camel.k.main.ApplicationRuntime$MainListenerAdapter.lambda$invokeListeners$0(ApplicationRuntime.java:176)
            at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183)
            at java.base/java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:357)
            at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485)
            at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474)
            at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150)
            at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173)
            at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
            at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497)
            at org.apache.camel.k.main.ApplicationRuntime$MainListenerAdapter.invokeListeners(ApplicationRuntime.java:175)
            at org.apache.camel.k.main.ApplicationRuntime$MainListenerAdapter.beforeConfigure(ApplicationRuntime.java:140)
            at org.apache.camel.main.BaseMainSupport.postProcessCamelContext(BaseMainSupport.java:604)
            at org.apache.camel.main.BaseMainSupport.initCamelContext(BaseMainSupport.java:440)
            at org.apache.camel.k.main.ApplicationRuntime$MainAdapter.doInit(ApplicationRuntime.java:197)
            at org.apache.camel.support.service.BaseService.init(BaseService.java:83)
            at org.apache.camel.support.service.BaseService.start(BaseService.java:111)
            at org.apache.camel.main.MainSupport.run(MainSupport.java:83)
            at org.apache.camel.k.main.ApplicationRuntime.run(ApplicationRuntime.java:70)
            at org.apache.camel.k.main.Application.main(Application.java:42)
    2020-06-05 12:16:56.202 INFO  [Camel Thread #0 - CamelHangupInterceptor] MainSupport$HangupInterceptor - Received hang up - stopping the main instance.

    We are using the kamel cli (1.0.0-nightly.202005130003) to deploy the operator.

    The integration platform has the following configuration (in helmfile):

        values:
          - resources:
              - apiVersion: camel.apache.org/v1
                kind: IntegrationPlatform
                metadata:
                  namespace: scraper
                  name: camel-k
                spec:
                  profile: Knative
                  build:
                    # todo: check if buildah now works
                    publishStrategy: Kaniko
    
                    registry:
                      address: xxx.com
                      secret: integration-platform-secret
    
                  # needed for nightly build
                  configuration:
                    - type: repository
                      value: xxx.com

    The integrations definitions look like the following:

        values:
          - resources:
            - apiVersion: camel.apache.org/v1
              kind: Integration
              metadata:
                namespace: scraper
                name: resource-request-route-integration
              spec:
                dependencies:
                - camel:jackson
                - camel:sql
                - mvn:com.fasterxml.jackson.core:jackson-core:jar:2.11.0
                - mvn:org.eclipse.rdf4j:rdf4j-core:pom:3.2.0
                - mvn:org.eclipse.rdf4j:rdf4j-rio-jsonld:jar:3.2.0
                - mvn:org.apache.commons:commons-lang3:jar:3.10
                - mvn:mysql:mysql-connector-java:jar:8.0.20
    
                sources:
                - name: ResourceRequestRouteBuilder.java
                  content: |
                    import org.apache.camel.builder.RouteBuilder;
                    ...list of dependencies...
    
    
                    public class ResourceRequestRouteBuilder extends RouteBuilder {
                        @Override
                        public void configure() throws Exception {
                from("timer:start?delay=0&period=43200000")
        ...

    I recognized that the camel-k-runtime 1.3.0-SNAPSHOT was updated yesterday. Is this related to the error? If yes does somebody know what to do?

    Thanks :)

    Nicola Ferraro
    @nicolaferraro
    Hi @anerathil , sorry for the issue, the nightly depends on snapshots that have been changed.. we should try to avoid this in the future
    Anyway, we're about to release Camel K 1.0.0 today, I'll publish more info here: apache/camel-k#1498
    Martin Nigbur
    @anerathil
    Hey, thanks for the clarification.
    Happy to hear about the 1.0.0 release 😍
    michaelwjoyner
    @michaelwjoyner
    Congrats Nicola for the 1.0.0 release WOOT!