chore: update release manifests and examples with new spec (#632)

* update manifests and examples * add namespace int kustomize * move ns above * rename gateways and sensors
argoproj · May 7, 2020 · ef70ec0 · ef70ec0
1 parent 09f0912
commit ef70ec0
Show file tree

Hide file tree

Showing 106 changed files with 413 additions and 1,195 deletions.
diff --git a/docs/demo/notebooks.md b/docs/demo/notebooks.md
@@ -91,12 +91,7 @@ In this demo, we are going to set up an image processing pipeline using 2 notebo
           name: webhook-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0-rc
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: webhook-gateway

diff --git a/docs/triggers/argo-workflow.md b/docs/triggers/argo-workflow.md
@@ -30,12 +30,7 @@ Argo workflow is K8s custom resource which help orchestrating parallel jobs on K
           name: webhook-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: webhook-gateway

diff --git a/docs/triggers/http-trigger.md b/docs/triggers/http-trigger.md
@@ -185,12 +185,7 @@ to invoke OpenFaas function.
           name: redis-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: redis-gateway
@@ -242,12 +237,7 @@ Similar to REST API calls, you can easily invoke Kubeless functions using HTTP t
           name: nats-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: nats-gateway

diff --git a/docs/triggers/k8s-object-trigger.md b/docs/triggers/k8s-object-trigger.md
@@ -33,12 +33,7 @@ set up event-driven pipelines for existing workloads.
           name: webhook-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: webhook-gateway

diff --git a/docs/triggers/kafka-trigger.md b/docs/triggers/kafka-trigger.md
@@ -21,12 +21,7 @@ The Kafka trigger specification is available [here](https://github.com/argoproj/
           name: minio-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: minio-gateway

diff --git a/docs/triggers/nats-trigger.md b/docs/triggers/nats-trigger.md
@@ -21,12 +21,7 @@ The NATS trigger specification is available [here](https://github.com/argoproj/a
           name: minio-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.13.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: minio-gateway

diff --git a/docs/tutorials/09-events-over-nats.md b/docs/tutorials/09-events-over-nats.md
@@ -73,31 +73,11 @@ Up until now, you have seen the gateway dispatch events to sensor over HTTP. In
           eventSourceRef:
             name: webhook-event-source
           template:
-            metadata:
-              name: webhook-gateway
-              labels:
-                gateway-name: webhook-gateway
-            spec:
-              containers:
-                - name: gateway-client
-                  image: argoproj/gateway-client:v0.14.0
-                  imagePullPolicy: Always
-                  command: ["/bin/gateway-client"]
-                - name: webhook-events
-                  image: argoproj/webhook-gateway:v0.14.0
-                  imagePullPolicy: Always
-                  command: ["/bin/webhook-gateway"]
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           service:
-            metadata:
-              name: webhook-gateway-svc
-            spec:
-              selector:
-                gateway-name: webhook-gateway
-              ports:
-                - port: 12000
-                  targetPort: 12000
-              type: LoadBalancer
+            ports:
+              - port: 12000
+                targetPort: 12000
           subscribers:
             nats:
               - name: webhook-sensor
@@ -127,12 +107,7 @@ Up until now, you have seen the gateway dispatch events to sensor over HTTP. In
           name: webhook-sensor
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.14.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: webhook-gateway
@@ -213,31 +188,11 @@ You can easily set up a gateway to send events over both HTTP and NATS,
           eventSourceRef:
             name: webhook-event-source
           template:
-            metadata:
-              name: webhook-gateway
-              labels:
-                gateway-name: webhook-gateway
-            spec:
-              containers:
-                - name: gateway-client
-                  image: argoproj/gateway-client:v0.14.0
-                  imagePullPolicy: Always
-                  command: ["/bin/gateway-client"]
-                - name: webhook-events
-                  image: argoproj/webhook-gateway:v0.14.0
-                  imagePullPolicy: Always
-                  command: ["/bin/webhook-gateway"]
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           service:
-            metadata:
-              name: webhook-gateway-svc
-            spec:
-              selector:
-                gateway-name: webhook-gateway
-              ports:
-                - port: 12000
-                  targetPort: 12000
-              type: LoadBalancer
+            ports:
+              - port: 12000
+                targetPort: 12000
           subscribers:
             http:
               - "http://webhook-time-filter-sensor.argo-events.svc:9300/"
@@ -256,12 +211,7 @@ You can easily set up a gateway to send events over both HTTP and NATS,
           name: webhook-sensor-over-http-and-nats
         spec:
           template:
-            spec:
-              containers:
-                - name: sensor
-                  image: argoproj/sensor:v0.14.0
-                  imagePullPolicy: Always
-              serviceAccountName: argo-events-sa
+            serviceAccountName: argo-events-sa
           dependencies:
             - name: test-dep
               gatewayName: webhook-gateway

diff --git a/examples/gateways/amqp.yaml b/examples/gateways/amqp.yaml
@@ -1,27 +1,13 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: amqp-gateway
+  name: amqp
 spec:
   type: amqp
   eventSourceRef:
     name: amqp-event-source
   template:
-    metadata:
-      name: amqp-gateway
-      labels:
-        gateway-name: amqp-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: amqp-events
-          image: argoproj/amqp-gateway:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/amqp-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   subscribers:
     http:
       - "http://amqp-sensor.argo-events.svc:9300/"
diff --git a/examples/gateways/aws-sns.yaml b/examples/gateways/aws-sns.yaml
@@ -1,37 +1,17 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: aws-sns-gateway
+  name: aws-sns
 spec:
   type: sns
   eventSourceRef:
     name: aws-sns-event-source
   template:
-    metadata:
-      name: aws-sns-gateway
-      labels:
-        gateway-name: aws-sns-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.13.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: aws-sns-events
-          image: argoproj/aws-sns-gateway:v0.13.0
-          imagePullPolicy: Always
-          command: ["/bin/aws-sns-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   service:
-    metadata:
-      name: aws-sns-gateway-svc
-    spec:
-      selector:
-        gateway-name: aws-sns-gateway
-      ports:
-        - port: 12000
-          targetPort: 12000
-      type: LoadBalancer
+    ports:
+      - port: 12000
+        targetPort: 12000
   subscribers:
     http:
       - "http://aws-sns-sensor.argo-events.svc:9300/"
diff --git a/examples/gateways/aws-sqs.yaml b/examples/gateways/aws-sqs.yaml
@@ -1,28 +1,13 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: aws-sqs-gateway
+  name: aws-sqs
 spec:
-  replica: 1
   type: sqs
   eventSourceRef:
     name: aws-sqs-event-source
   template:
-    metadata:
-      name: aws-sqs-gateway
-      labels:
-        gateway-name: aws-sqs-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: aws-sqs-events
-          image: argoproj/aws-sqs-gateway:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/aws-sqs-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   subscribers:
     http:
       - "http://aws-sqs-sensor.argo-events.svc:9300/"
diff --git a/examples/gateways/azure-events-hub.yaml b/examples/gateways/azure-events-hub.yaml
@@ -1,27 +1,13 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: azure-events-hub-gateway
+  name: azure-events-hub
 spec:
   type: azureEventsHub
   eventSourceRef:
     name: azure-events-hub-event-source
   template:
-    metadata:
-      name: azure-events-hub-gateway
-      labels:
-        gateway-name: azure-events-hub-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: azure-events-hub-events
-          image: argoproj/azure-events-hub-gateway:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/azure-events-hub-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   subscribers:
     http:
       - "http://azure-events-hub-sensor.argo-events.svc:9300/"
diff --git a/examples/gateways/calendar.yaml b/examples/gateways/calendar.yaml
@@ -1,27 +1,13 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: calendar-gateway
+  name: calendar
 spec:
   type: calendar
   eventSourceRef:
     name: calendar-event-source
   template:
-    metadata:
-      name: calendar-gateway
-      labels:
-        gateway-name: calendar-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: calendar-events
-          image: argoproj/calendar-gateway:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/calendar-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   subscribers:
     http:
       - "http://calendar-sensor.argo-events:9300/"
diff --git a/examples/gateways/emitter.yaml b/examples/gateways/emitter.yaml
@@ -1,27 +1,13 @@
 apiVersion: argoproj.io/v1alpha1
 kind: Gateway
 metadata:
-  name: emitter-gateway
+  name: emitter
 spec:
   type: emitter
   eventSourceRef:
     name: emitter-event-source
   template:
-    metadata:
-      name: emitter-gateway
-      labels:
-        gateway-name: emitter-gateway
-    spec:
-      containers:
-        - name: gateway-client
-          image: argoproj/gateway-client:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/gateway-client"]
-        - name: emitter-events
-          image: argoproj/emitter-gateway:v0.14.0
-          imagePullPolicy: Always
-          command: ["/bin/emitter-gateway"]
-      serviceAccountName: argo-events-sa
+    serviceAccountName: argo-events-sa
   subscribers:
     http:
       - "http://emitter-sensor.argo-events.svc:9300/"