Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    pjcubero
    @pjcubero
    Hi, anyone knows how to avoid that kamel k integration restarts every X seconds without any modification?
    2 replies
    Andrew Mak
    @makandre_gitlab
    When I'm pushing data to a knative:channel, the message is transformed into a CloudEvent (ce_ headers generated) which is nice. But I can't seem to add any extra headers (I'm using set-header). Is there some special way to set extension headers?
    29 replies
    Aleksander Slominski
    @aslom

    Is there any way I can disable go run cmd/kamel/main.go install from creating camel-k-operator deployment? i do not have any operator installed instead I run with go run cmd/manager/main.go operator

    k get  deployment camel-k-operator
    NAME               READY   UP-TO-DATE   AVAILABLE   AGE
    camel-k-operator   0/1     1            0           11m
    
    k get po
    NAME                                       READY   STATUS             RESTARTS   AGE
    camel-k-kit-bt3dh9eg10lbubv72g70-1-build   0/1     Completed          0          18m
    camel-k-kit-bt3dk96g10lbubv72g80-1-build   0/1     Completed          0          10m
    camel-k-kit-bt3dm0ug10lchn4bpkg0-1-build   0/1     Completed          0          8m41s
    camel-k-operator-74b894d899-l7w8l          0/1     ImagePullBackOff   0          11m

    Everything seems ot work fine after I delete that deployment - it was failign as it uses snapshot image:

    k get deployment camel-k-operator -o yaml
    ...
            image: docker.io/apache/camel-k:1.1.0-SNAPSHOT
            imagePullPolicy: IfNotPresent
            name: camel-k-operator
    ...

    The only config I am doing is with go run cmd/kamel/main.go install --force --maven-repository http://repository.apache.org/content/groups/snapshots-group@id\=apache@snapshots@noreleases --olm=false and I verified it recreated camel-k-operator deployment

    3 replies
    Aleksander Slominski
    @aslom

    BTW: I was not able to change docker registry used with install - it seems to be ignored in OCP 4.4 and the registry used is image-registry.openshift-image-registry.svc:5000

    I can see that there is lot of docker related secrets but I can not find form operator log or builder which secret it uses and why

    k get secret
    NAME                               TYPE                                  DATA   AGE
    builder-dockercfg-vgdrc            kubernetes.io/dockercfg               1      32m
    builder-token-45vcd                kubernetes.io/service-account-token   4      32m
    builder-token-dsnn7                kubernetes.io/service-account-token   4      32m
    camel-k-operator-dockercfg-6txk4   kubernetes.io/dockercfg               1      3m49s
    camel-k-operator-dockercfg-dgb2n   kubernetes.io/dockercfg               1      20m
    camel-k-operator-token-jn72r       kubernetes.io/service-account-token   4      3m49s
    camel-k-operator-token-q9kxq       kubernetes.io/service-account-token   4      20m
    camel-k-operator-token-tzmvj       kubernetes.io/service-account-token   4      20m
    camel-k-operator-token-xcl2p       kubernetes.io/service-account-token   4      3m49s
    default-dockercfg-kh8ts            kubernetes.io/dockercfg               1      32m
    default-token-lvbzr                kubernetes.io/service-account-token   4      32m
    default-token-v8mk6                kubernetes.io/service-account-token   4      32m
    deployer-dockercfg-8fdsr           kubernetes.io/dockercfg               1      32m
    deployer-token-6x6ds               kubernetes.io/service-account-token   4      32m
    deployer-token-mxsbb               kubernetes.io/service-account-token   4      32m
    istio.builder                      istio.io/key-and-cert                 3      32m
    istio.camel-k-operator             istio.io/key-and-cert                 3      20m
    istio.default                      istio.io/key-and-cert                 3      32m
    istio.deployer                     istio.io/key-and-cert                 3      32m
    2 replies
    Rahul Kiran Gaddam
    @rahgadda
    Does quarkus have any framework like OData to support RestAPI? I am looking for a project similar to Odata that is pure rest and not alternatives like GraphQL
    1 reply
    Pedro Freitas
    @pdefreitas
    Hello! I'm using Camel K with Knative and I'm wondering when you use CamelSource kind, injecting a sink it overrides knative trait specified configuration section. Can anyone share me an example of how can I do it or is this expected behavior?
    Pedro Freitas
    @pdefreitas
    I am trying to do something fun with Jetty Websockets and it seems like knative is autoloading vert.x http by detecting something on my CamelSource integration, that is why I'm trying to get in handle of auto value of knative trait:
    RuntimeSupport - Found customizer org.apache.camel.k.http.PlatformHttpServiceContextCustomizer@3241713e with id platform-http from service definition
    Luca Burgazzoli
    @lburgazzoli
    @pdefreitas I think I understand what you’re trying to achieve but would be nice if you can open an issue with some description of the use case and some code can help to better understand and advise
    pjcubero
    @pjcubero
    I have seen that there is a new version of knative, 0.17, in this version is solved the issue with subscriptions?
    pjcubero
    @pjcubero

    I have seen that there is a new version of knative, 0.17, in this version is solved the issue with subscriptions?

    I see that still there is the error... Cannot reconcile Integration creacion-pacientes: error executing post actions: error during replace resource: could not create or replace resource channel-a28-creacion-pacientes: no matches for kind "Subscription" in version "messaging.knative.dev/v1alpha1". do you know when will be solved?

    Luca Burgazzoli
    @lburgazzoli
    @pjcubero see apache/camel-k#1636
    pjcubero
    @pjcubero

    @pjcubero see apache/camel-k#1636

    But, if I remove the suscription and I add to("knative:channel/channel-xx"), this not working. Which has been the solution implemented?

    Luca Burgazzoli
    @lburgazzoli
    I don't understand what you are asking now.
    Your question was when it will be solved, and the answer is that is has been solved and the fix will be available in the next patch release 1.1.1
    Andrea Cosentino
    @oscerd
    the fix is not released yet.
    pjcubero
    @pjcubero

    the fix is not released yet.

    Ok, the fix is not released, ok, then will be solved in knative 1.1.1?

    Luca Burgazzoli
    @lburgazzoli
    as per the issue, yes the fix will be present in the camel-k v1.1.1
    pjcubero
    @pjcubero

    as per the issue, yes the fix will be present in the camel-k v1.1.1

    Ok, clear now... sorry by my confussion...

    Andrew Mak
    @makandre_gitlab
    What is the proper way to specify the number of replicas when running an integration with kamel run?
    4 replies
    Martin Nigbur
    @anerathil

    Hey guys, got a question regarding camel-k 1.1.0 and knative 0.17.
    I deployed a KafkaChannel:

      values:
      - resources:
        - apiVersion: messaging.knative.dev/v1beta1
          kind: KafkaChannel
          metadata:
            name: events
            namespace: data-platform-gdelt-system
            annotations:
              eventing.knative.dev/scope: namespace
          spec:
            numPartitions: 3
            replicationFactor: 1

    ... as well as a simple integration:

      from("timer:start?period=1000")
        .setBody(constant("test"))
        .process(exchange -> {
          final var inboundMessage = exchange.getIn();
          final var message = exchange.getMessage();
    
          /*
          ...
          */
    
          message.getHeaders().clear();
    
          message.setHeader("CE-ID", "eventID");
          message.setHeader("CE-Source", "/2ac27a78-8b0d-4633-b1c7-8182d2df02f8/data-platform-data-system/gdelt");
          message.setHeader("CE-SpecVersion", "1.0");
          message.setHeader("CE-Type", "com.company.ResourceRequested");
          message.setHeader("CE-Time", "eventGenerationTimestamp");
          message.setHeader("CE-Subject", "requestIRI");
          message.setHeader("CE-DataContentType", "application/ld+json");
          message.setHeader("CE-System", "gdelt2");
    
        })
      .to("knative:channel/events");

    Result is: The integration is throwing 404's all the time:
    org.apache.camel.CamelException: HTTP operation failed invoking http://events-kn-channel.data-platform-gdelt-system.svc.cluster.local:80/ with statusCode: 404, statusMessage: Not Found

    Also the kafka-ch-dispatcher is throwing errors:
    E0901 13:31:48.392144 1 leaderelection.go:331] error retrieving resource lock knative-eventing/kafkachannel-dispatcher.knative.dev-eventing-contrib-kafka-channel-pkg-reconciler-dispatcher.reconciler.00-of-01: leases.coordination.k8s.io "kafkachannel-dispatcher.knative .dev-eventing-contrib-kafka-channel-pkg-reconciler-dispatcher.reconciler.00-of-01" is forbidden: User "system:serviceaccount:data-platform-gdelt-system:kafka-ch-dispatcher" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "knative-eventing"

    As i'am not 100% familiar with K8s i'm not totally clear about how to solve that. Is this related to knative 0.17?
    Would be nice if you guys could help me :)

    8 replies
    Corey
    @c1505
    How do we go about troubleshooting an integration when no pods spin up ? I am trying to get anything to work with the jira component and all I get is that there is an error when I look using kamel get or kamel describe integration.
    Luca Burgazzoli
    @lburgazzoli
    do you mean you don't have any pod running because it fails or no pods are created at all ?
    if no pods, then you'd need to check the logs of the operator
    Corey
    @c1505
    no pods are created at all. thanks . checked the operator and it looks like there is a dependency resolution problem.
    [ERROR] Failed to execute goal on project camel-k-integration: Could not resolve dependencies for project org.apache.camel.k.integration:camel-k-integration:jar:1.1.0: The following artifacts could not be resolved: com.atlassian.jira:jira-rest-java-client-api:jar:5.1.6, com.atlassian.jira:jira-rest-java-client-core:jar:5.1.6: Failure to find com.atlassian.jira:jira-rest-java-client-api:jar:5.1.6 in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced -> [Help 1]
    Luca Burgazzoli
    @lburgazzoli
    if you are using jira, it may be required to add an additional repo I think
    because the library used by the component is hosted on the atalassian maven repo
    Corey
    @c1505
    thanks. Is there somewhere in the docs that I should have seen that or a way that I would know without asking the question ? Just trying to figure out how to do things as I look at other integrations too. I am looking at this component doc https://camel.apache.org/components/latest/jira-component.html .
    Luca Burgazzoli
    @lburgazzoli
    mh, we should probably add a note to the doc
    Can you confirm that by adding the atlassian repo it does work ? https://github.com/apache/camel/blob/259ad4f098438588ee2d265a9db20d539f326b75/pom.xml#L151-L161
    Corey
    @c1505
    How do I do that? I see that I can specify dependencies when running the integration. Unsure how to add a different source with this.
    you can add a list of repositories you want to include upon installation or by editing the config map that holds the maven settings
    Andrew Mak
    @makandre_gitlab
    Hi, when I have an integration consuming from a knative channel, and there's multiple pods of that integration, what's the expected behaviour? Can they get messages in round robin fashion? Right now it seems one pod always get all the messages
    1 reply
    pjcubero
    @pjcubero
    Hi, I have some integrations in camel-k, over minikube, one question, I have deployed also ISTIO, is there any way to see the ISTIO dashboard?
    4 replies
    Martin Nigbur
    @anerathil
    Hey, is there already a release date for 1.1.1? :)
    pjcubero
    @pjcubero
    Hi, I have some questions about Minikube, do you know if there is some room about this matter?
    Luca Burgazzoli
    @lburgazzoli
    @pjcubero https://minikube.sigs.k8s.io/docs/ there's a dedicated channel on the official kubernetes slack
    pjcubero
    @pjcubero

    @pjcubero https://minikube.sigs.k8s.io/docs/ there's a dedicated channel on the official kubernetes slack

    I have found a google group, is this what you tell me?

    Luca Burgazzoli
    @lburgazzoli
    there's both a google group and a slack channel, see https://minikube.sigs.k8s.io/community/
    pjcubero
    @pjcubero

    there's both a google group and a slack channel, see https://minikube.sigs.k8s.io/community/

    Do you know how can I get one invitation to belong to the chat group?

    Luca Burgazzoli
    @lburgazzoli
    Jawad Ahmad
    @jawwad124_gitlab
    Guys, can we run Camel K on AWS EKS service ?
    I am trying to find out but unable to see any concrete information or guideline on Camel K docs.
    I need to a run a POC to develop a Salesforce connector application, I already have a working prototype with ECS Fargate and Spring Boot.
    But i am not sure how this will work with Camel K and EKS.
    Jawad Ahmad
    @jawwad124_gitlab
    Anyone ?
    coricko
    @coricko
    @jawwad124_gitlab, yeah you can. Camel K cannot currently talk to ECR, but if you follow the instructions for configuring a different registry (I did it with Docker Hub), then that'll work
    Jawad Ahmad
    @jawwad124_gitlab
    Thanks @coricko , I will give it a try with Github packages.
    I am hoping that it will work with the private docker registry If i will have setup later.
    Jawad Ahmad
    @jawwad124_gitlab

    Failed to execute goal on project camel-k-integration: Could not resolve dependencies for project org.apache.camel.k.integration:camel-k-integration:jar:1.1.0: Failed to collect dependencies at com.github.jawad-r3

    I am trying to fetch the maven dependency from jitpack. I have created the config map with settings.xml of my jitpack user and from my local machine i am able to fetch the dependency. But its giving authorization error while running the kamel integration.