(#5490) Move deprecated v1alpha1.KameletBinding tests to v1.Pipe

e2e/yaks/common/apache-kamelet-catalog/yaks-config.yaml

@@ -15,10 +15,6 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-# Run integration test:
-#
-# yaks run -v ./e2e/yaks/common/apache-kamelet-catalog/kamelet.feature
-
 config:
   namespace:
     temporary: true

e2e/yaks/common/kamelet-beans/kamelet-beans.feature

@@ -7,7 +7,7 @@ Feature: Kamelets can declare local beans
 
   Scenario: Kamelets templates can use beans
     Given bind Kamelet beans-source to uri log:info
-    When create KameletBinding binding
-    Then KameletBinding binding should be available
+    When create Pipe binding
+    Then Pipe binding should be available
     Then Camel K integration binding should be running
     Then Camel K integration binding should print Bean time is 0!

e2e/yaks/common/kamelet-data-types/event-binding.yaml → e2e/yaks/common/kamelet-data-types/event-pipe.yaml

@@ -15,10 +15,10 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: event-binding
+  name: event-pipe
 spec:
   source:
     ref:
@@ -40,4 +40,4 @@ spec:
       name: event-sink
     dataTypes:
       in:
-        format: "text-plain"
+        format: "text-plain"

e2e/yaks/common/kamelet-data-types/kamelet-data-types.feature

@@ -6,17 +6,17 @@ Feature: Kamelets with data types
       | delayBetweenAttempts | 4000 |
 
   Scenario: Kamelet event data type conversion
-    Given load KameletBinding event-binding.yaml
-    Given Camel K integration event-binding is running
-    Then Camel K integration event-binding should print BodyType: byte[], Body: Hello from Camel K!
-    Then Camel K integration event-binding should print BodyType: String, Body: Hello from Camel K!
+    Given load Pipe event-pipe.yaml
+    Given Camel K integration event-pipe is running
+    Then Camel K integration event-pipe should print BodyType: byte[], Body: Hello from Camel K!
+    Then Camel K integration event-pipe should print BodyType: String, Body: Hello from Camel K!
 
   Scenario: Kamelet timer-to-log conversion
-    Given load KameletBinding timer-to-log.yaml
+    Given load Pipe timer-to-log.yaml
     Given Camel K integration timer-to-log is running
     Then Camel K integration timer-to-log should print BodyType: byte[], Body: Hello from Camel K!
     Then Camel K integration timer-to-log should print BodyType: String, Body: Hello from Camel K!
 
   Scenario: Remove resources
-    Given delete KameletBinding event-binding
-    Given delete KameletBinding timer-to-log
+    Given delete Pipe event-pipe
+    Given delete Pipe timer-to-log

e2e/yaks/common/kamelet-data-types/timer-to-log.yaml

@@ -15,8 +15,8 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
   name: timer-to-log
 spec:

e2e/yaks/common/kamelet-data-types/yaks-config.yaml

@@ -29,7 +29,7 @@ config:
         - name: INTEGRATION_LOGS
           level: INFO
     resources:
-      - event-binding.yaml
+      - event-pipe.yaml
       - timer-to-log.yaml
 pre:
 - name: installation

e2e/yaks/common/kamelet-no-properties/kamelet-no-props.feature → e2e/yaks/common/kamelet-no-properties/kamelet-no-properties.feature

@@ -22,11 +22,11 @@ from:
   Scenario: Bind Kamelet to service
     Given create Kubernetes service greeting-service with target port 8080
     And bind Kamelet no-props-source to uri log:info
-    When create KameletBinding no-props-source-uri
-    Then KameletBinding no-props-source-uri should be available
+    When create Pipe no-props-source-uri
+    Then Pipe no-props-source-uri should be available
     Then Camel K integration no-props-source-uri should be running
     Then Camel K integration no-props-source-uri should print Hello World
 
   Scenario: Remove resources
     Given delete Kubernetes service greeting-service
-    Given delete KameletBinding no-props-source-uri
+    Given delete Pipe no-props-source-uri

e2e/yaks/common/kamelet-binding-autoload/kamelet-autoload-specific.feature → e2e/yaks/common/kamelet-pipe-autoload/kamelet-pipe-autoload-specific.feature

@@ -7,17 +7,17 @@ Feature: Camel K can load specific secrets for Kamelets
       | maxAttempts          | 40   |
       | delayBetweenAttempts | 3000 |
 
-  Scenario: KameletBinding can load specific settings for Kamelet
+  Scenario: Pipe can load specific settings for Kamelet
     Given create Kubernetes service stub-service-2 with target port 8080
     And bind Kamelet timer-source to uri http://stub-service-2.${YAKS_NAMESPACE}.svc.cluster.local/specific
-    And KameletBinding source properties
+    And Pipe source properties
       | id  | specific |
-    When create KameletBinding binding-specific
-    Then KameletBinding binding-specific should be available
+    When create Pipe binding-specific
+    Then Pipe binding-specific should be available
 
  Scenario: Verify specific binding
     Given HTTP server "stub-service-2"
     And HTTP server timeout is 600000 ms
     Then expect HTTP request body: specific
     And receive POST /specific
-    And delete KameletBinding binding-specific
+    And delete Pipe binding-specific

e2e/yaks/common/kamelet-binding-autoload/kamelet-autoload.feature → e2e/yaks/common/kamelet-pipe-autoload/kamelet-pipe-autoload.feature

@@ -7,11 +7,11 @@ Feature: Camel K can load default secrets for Kamelets
       | maxAttempts          | 40   |
       | delayBetweenAttempts | 3000 |
 
-  Scenario: KameletBinding can load default settings for Kamelet
+  Scenario: Pipe can load default settings for Kamelet
     Given create Kubernetes service stub-service with target port 8080
     And bind Kamelet timer-source to uri http://stub-service.${YAKS_NAMESPACE}.svc.cluster.local/default
-    When create KameletBinding binding
-    Then KameletBinding binding should be available
+    When create Pipe binding
+    Then Pipe binding should be available
 
  Scenario: Verify default binding
     Given HTTP server "stub-service"
@@ -21,4 +21,4 @@ Feature: Camel K can load default secrets for Kamelets
 
  Scenario: Remove resources
     Given delete Kubernetes service stub-service
-    Given delete KameletBinding binding
+    Given delete Pipe binding

e2e/yaks/common/kamelet-pipe-broker/kamelet-pipe-broker.feature

@@ -0,0 +1,14 @@
+Feature: Camel K can bind Kamelets to the broker
+
+  Background:
+    Given Camel K resource polling configuration
+      | maxAttempts          | 40   |
+      | delayBetweenAttempts | 3000 |
+
+  Scenario: Sending event to the custom broker with Pipe
+    Given Camel K integration logger-sink-pipe is running
+    Then Camel K integration logger-sink-pipe should print message: Hello Custom Event from sample-broker
+
+  Scenario: Remove resources
+    Given delete Camel K integration timer-source-pipe
+    Given delete Camel K integration logger-sink-pipe

e2e/yaks/common/kamelet-binding-broker/logger-sink-binding-br.yaml → e2e/yaks/common/kamelet-pipe-broker/logger-sink-pipe.yaml

@@ -15,10 +15,10 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: logger-sink-binding-br
+  name: logger-sink-pipe
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding-broker/timer-source-binding-br.yaml → e2e/yaks/common/kamelet-pipe-broker/timer-source-pipe.yaml

@@ -15,10 +15,10 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: timer-source-binding-br
+  name: timer-source-pipe
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding-broker/yaks-config.yaml → e2e/yaks/common/kamelet-pipe-broker/yaks-config.yaml

@@ -25,10 +25,10 @@ pre:
     kubectl apply -f timer-source.kamelet.yaml -n $YAKS_NAMESPACE
     kubectl apply -f logger-sink.kamelet.yaml -n $YAKS_NAMESPACE
 
-    kubectl apply -f timer-source-binding-br.yaml -n $YAKS_NAMESPACE
-    kubectl apply -f logger-sink-binding-br.yaml -n $YAKS_NAMESPACE
-    kubectl wait kameletbinding timer-source-binding-br --for=condition=Ready --timeout=15m -n $YAKS_NAMESPACE
-    kubectl wait kameletbinding logger-sink-binding-br --for=condition=Ready --timeout=15m -n $YAKS_NAMESPACE
+    kubectl apply -f timer-source-pipe.yaml -n $YAKS_NAMESPACE
+    kubectl apply -f logger-sink-pipe.yaml -n $YAKS_NAMESPACE
+    kubectl wait pipe timer-source-pipe --for=condition=Ready --timeout=5m -n $YAKS_NAMESPACE
+    kubectl wait pipe logger-sink-pipe --for=condition=Ready --timeout=5m -n $YAKS_NAMESPACE
 post:
   - name: print dump
     if: env:CI=true && failure()

e2e/yaks/common/kamelet-binding-http/kamelet-binding-http.feature → e2e/yaks/common/kamelet-pipe-http/kamelet-pipe-http.feature

@@ -5,11 +5,11 @@ Feature: Camel K can bind Kamelets via HTTP
       | maxAttempts          | 40   |
       | delayBetweenAttempts | 3000 |
 
-  Scenario: KameletBinding to a HTTP URI should use CloudEvents
+  Scenario: Pipe to a HTTP URI should use CloudEvents
     Given Camel K integration display is running
     Then Camel K integration display should print type: org.apache.camel.event
     Then Camel K integration display should print Hello
 
   Scenario: Remove resources
     Given delete Camel K integration display
-    Given delete KameletBinding timer-source-binding-display
+    Given delete Pipe timer-source-pipe

e2e/yaks/common/kamelet-binding-http/timer-source-binding-display.yaml → e2e/yaks/common/kamelet-pipe-http/timer-source-pipe.yaml

@@ -18,7 +18,7 @@
 apiVersion: camel.apache.org/v1
 kind: Pipe
 metadata:
-  name: timer-source-binding-display
+  name: timer-source-pipe
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding-http/yaks-config.yaml → e2e/yaks/common/kamelet-pipe-http/yaks-config.yaml

@@ -15,10 +15,6 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-# Run integration test:
-#
-# yaks run -v ./e2e/yaks/common/kamelet-binding-http/kamelet-binding-http.feature
-
 config:
   namespace:
     temporary: true
@@ -28,8 +24,8 @@ pre:
     kubectl apply -f timer-source.kamelet.yaml -n $YAKS_NAMESPACE
 
     kamel run display.yaml -w -n $YAKS_NAMESPACE
-    cat timer-source-binding-display.yaml | sed  's/{namespace}/'"${YAKS_NAMESPACE}"'/' | kubectl apply -n $YAKS_NAMESPACE -f -
-    kubectl wait pipe timer-source-binding-display --for=condition=Ready --timeout=15m -n $YAKS_NAMESPACE
+    cat timer-source-pipe.yaml | sed  's/{namespace}/'"${YAKS_NAMESPACE}"'/' | kubectl apply -n $YAKS_NAMESPACE -f -
+    kubectl wait pipe timer-source-pipe --for=condition=Ready --timeout=15m -n $YAKS_NAMESPACE
 post:
   - name: print dump
     if: env:CI=true && failure()

e2e/yaks/common/kamelet-binding-property-encoding/properties.feature → e2e/yaks/common/kamelet-pipe-properties/kamelet-pipe-properties.feature

@@ -9,7 +9,7 @@ Feature: Ensure that Kamelets support multiline configuration
 
   Scenario: Wait for binding to start
     Given create Kubernetes service probe-service with target port 8080
-    Then Camel K integration properties-binding should be running
+    Then Camel K integration properties-pipe should be running
 
   Scenario: Verify binding
     Given HTTP server "probe-service"
@@ -26,4 +26,4 @@ Feature: Ensure that Kamelets support multiline configuration
 
   Scenario: Remove resources
     Given delete Kubernetes service probe-service
-    Given delete KameletBinding properties-binding
+    Given delete Pipe properties-pipe

e2e/yaks/common/kamelet-binding-property-encoding/properties-binding.yaml → e2e/yaks/common/kamelet-pipe-properties/properties-pipe.yaml

@@ -15,10 +15,11 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-kind: KameletBinding
-apiVersion: camel.apache.org/v1alpha1
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: properties-binding
+  name: properties-pipe
+
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding-property-encoding/yaks-config.yaml → e2e/yaks/common/kamelet-pipe-properties/yaks-config.yaml

@@ -22,8 +22,7 @@ pre:
 - name: installation
   run: |
     kubectl apply -f timer-source.kamelet.yaml -n $YAKS_NAMESPACE
-
-    kubectl apply -f properties-binding.yaml -n $YAKS_NAMESPACE
+    kubectl apply -f properties-pipe.yaml -n $YAKS_NAMESPACE
 post:
   - name: print dump
     if: env:CI=true && failure()

e2e/yaks/common/kamelet-pipe/kamelet-pipe.feature

@@ -0,0 +1,16 @@
+Feature: Camel K can bind Kamelets
+
+  Background:
+    Given Camel K resource polling configuration
+      | maxAttempts          | 40   |
+      | delayBetweenAttempts | 3000 |
+
+  Scenario: Running integration using a simple Kamelet with Pipes
+    Given Camel K integration timer-source-pipe is running
+    Given Camel K integration logger-sink-pipe is running
+    Then Camel K integration logger-sink-pipe should print message: Hello Kamelets
+
+  Scenario: Remove resources
+    Given delete Camel K integration timer-source-pipe
+    Given delete Camel K integration logger-sink-pipe
+

e2e/yaks/common/kamelet-binding/logger-sink-binding-kb.yaml → e2e/yaks/common/kamelet-pipe/logger-sink-pipe.yaml

@@ -15,10 +15,10 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: logger-sink-binding-kb
+  name: logger-sink-pipe
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding/timer-source-binding-kb.yaml → e2e/yaks/common/kamelet-pipe/timer-source-pipe.yaml

@@ -15,10 +15,10 @@
 # limitations under the License.
 # ---------------------------------------------------------------------------
 
-apiVersion: camel.apache.org/v1alpha1
-kind: KameletBinding
+apiVersion: camel.apache.org/v1
+kind: Pipe
 metadata:
-  name: timer-source-binding-kb
+  name: timer-source-pipe
 spec:
   source:
     ref:

e2e/yaks/common/kamelet-binding/yaks-config.yaml → e2e/yaks/common/kamelet-pipe/yaks-config.yaml

@@ -26,10 +26,10 @@ pre:
     kubectl apply -f timer-source.kamelet.yaml -n $YAKS_NAMESPACE
     kubectl apply -f logger-sink.kamelet.yaml -n $YAKS_NAMESPACE
 
-    kubectl apply -f timer-source-binding-kb.yaml -n $YAKS_NAMESPACE
-    kubectl apply -f logger-sink-binding-kb.yaml -n $YAKS_NAMESPACE
-    kubectl wait kameletbinding timer-source-binding-kb --for=condition=Ready --timeout=10m -n $YAKS_NAMESPACE
-    kubectl wait kameletbinding logger-sink-binding-kb --for=condition=Ready --timeout=10m -n $YAKS_NAMESPACE
+    kubectl apply -f timer-source-pipe.yaml -n $YAKS_NAMESPACE
+    kubectl apply -f logger-sink-pipe.yaml -n $YAKS_NAMESPACE
+    kubectl wait pipe timer-source-pipe --for=condition=Ready --timeout=5m -n $YAKS_NAMESPACE
+    kubectl wait pipe logger-sink-pipe --for=condition=Ready --timeout=5m -n $YAKS_NAMESPACE
 post:
   - name: print dump
     if: env:CI=true && failure()

e2e/yaks/common/kamelet-steps/kamelet-steps.feature

@@ -0,0 +1,13 @@
+Feature: Pipe can have multiple processing steps
+
+  Background:
+    Given Camel K resource polling configuration
+      | maxAttempts          | 40   |
+      | delayBetweenAttempts | 3000 |
+
+  Scenario: Data is transformed by the steps
+    Given Camel K integration steps-pipe is running
+    Then Camel K integration steps-pipe should print Hello Apache Camel
+
+  Scenario: Remove resources
+    Given delete Camel K integration steps-pipe