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

bad kamelet resolution using global flag

    XMLWordPrintable

Details

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

      in a new namespace ns:

      kamel install -n ns --global

      install the following kamelet in the same namespace (ns):

      apiVersion: camel.apache.org/v1alpha1
kind: Kamelet
metadata:
  name: my-own-timer-source 
  namespace: ns
  labels: 
    camel.apache.org/kamelet.type: "source"
spec:
  properties:
      message:
        type: string
  flow: 
    from:
      uri: timer:tick
      steps:
        - set-body:
            constant: "ciao"
        - to: "kamelet:sink"

      in a new namespace ns2:

      kamel install -n ns2 --skip-operator-setup --olm=false
      kamel run  -n ns2 files/timer-kamelet-usage.groovy
      Show
      in a new namespace ns: kamel install -n ns --global install the following kamelet in the same namespace (ns): apiVersion: camel.apache.org/v1alpha1 kind: Kamelet metadata: name: my-own-timer-source namespace: ns labels: camel.apache.org/kamelet.type: "source" spec: properties: message: type: string flow: from: uri: timer:tick steps: - set-body: constant: "ciao" - to: "kamelet:sink" in a new namespace ns2: kamel install -n ns2 --skip- operator -setup --olm= false kamel run -n ns2 files/timer-kamelet-usage.groovy

    Description

      The issue is related to this test: e2e/common/cli/global_kamelet_test.go.

      The target of this test is to show how camel-k-operator installed in global mode is able to run integration from a given namespace using kamelet created in a different namespace.

      In theory the kamelet resolution should happen because in the kamelet naspace is also included an integration platform which is a side effect of the operator installation command:

      kamel install -n ns --global

      assuming to create the kamelet in the ns namespace as well.

      I tried to run the test and also to reproduce the steps manually but i got an error. The log stated the kamelet was looked for only in openshift-operators namespace and in the integration namespace.

      I add that if in the integration namespace there is not the integration platform the integration run fails, but at the same time if the integration platform is there, no kamelet are looked outside of the integration namespace and OLM namespace.

      Attachments

        Activity

          People

            pcongius Pasquale Congiusti
            rhn-support-vgrazian Vitor Graziano
            Mario Majernik Mario Majernik
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: