| ... | ... | @@ -65,4 +65,13 @@ graph TD |
|
|
|
Home page: [LINK](https://argoproj.github.io/argo-events/)
|
|
|
|
Getting started: [LINK](https://argoproj.github.io/argo-events/quick_start/)
|
|
|
|
- This simple example shows how to spawn a new Argo workflow from an HTTP request with some payload
|
|
|
|
- We could make each Forwarding Agent to send a custom payload with the information of its providers and consumers, and then spawn a new workflow using that config |
|
|
\ No newline at end of file |
|
|
|
- We could make each Forwarding Agent to send a custom payload with the information of its providers and consumers, and then spawn a new workflow using that config
|
|
|
|
|
|
|
|
### EventSource
|
|
|
|
- Enable its own service to allow reachability from within the cluster to any pod
|
|
|
|
### Sensor
|
|
|
|
- Create k8s resource --> Pod
|
|
|
|
- Pods must point towards a `subdomain`
|
|
|
|
- This `subdomain` shall be the name of a headless `service` (without ClusterIP)
|
|
|
|
### Service
|
|
|
|
- Create a service whose selector is a pod's label (for now, use the `eventsource-name`, but as the EventSource has its own service, we don't need it in the same headless service anymore) |
|
|
\ No newline at end of file |
