Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-17004

Kamelets in namespace are not updated with the changes from operator

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • camel-k-1.6-GA
    • Camel-K-GA
    • Camel-K
    • None
    • False
    • False
    • % %
    • CK2
    • Todo
    • Undefined

    Description

      I had build 5 installed in my namespace and I undeployed the build 5 operator and installed build 7 operator in the same namespace. Between builds 5 and 7 there were changes in some kamelets, but the build 7 operator doesn't make the changes to the already deployed kamelets.

      For example aws-kinesis-source in build 5 has a following flow:

        flow:    
          from:    
            parameters:    
              accessKey: '{{accessKey}}'                                                                                                                                                                                  
              region: '{{region}}'    
              secretKey: '{{secretKey}}'    
            steps:    
            - to: kamelet:sink    
            uri: aws2-kinesis:{{stream}}
      

      When I undeploy the operator, the kamelets stay in the namespace and are not changed after deploying build 7. What I need to do is:
      1. delete kamelet: oc delete kamelet aws-kinesis-source
      2. redeploy operator: oc delete pod -l name=camel-k-operator

      Only then, the kamelet is updated to the one from build 7:

        flow:                                                                                                                                                                                                             
          from:    
            parameters:    
              accessKey: '{{accessKey}}'    
              region: '{{region}}'    
              secretKey: '{{secretKey}}'    
            steps:    
            - marshal:    
                json:    
                  library: Gson    
            - to: kamelet:sink    
            uri: aws2-kinesis:{{stream}}
      

      So there are actually two problems:
      1. kamelets are not deleted when the operator is deleted
      2. when a kamelet is deleted while the operator is running, it's not noticed and it is not recreated until the operator is restarted

      Attachments

        Activity

          People

            nicolaferraro Nicola Ferraro (Inactive)
            avano@redhat.com Andrej Vano
            Andrej Vano Andrej Vano
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: