github.com/argoproj/argo-events@v1.9.1/docs/FAQ.md (about)

     1  # FAQs
     2  
     3  **Q. How to get started with Argo Events?**
     4  
     5  **A**. The recommended way to get started with Argo Events is:
     6  
     7   1. Read the basic concepts about [EventBus](https://argoproj.github.io/argo-events/concepts/eventbus/), [Sensor](https://argoproj.github.io/argo-events/concepts/sensor/) and [Event Source](https://argoproj.github.io/argo-events/concepts/event_source/).
     8   2. Install Argo Events as outlined [here](https://argoproj.github.io/argo-events/installation/).
     9   3. Read the tutorials available [here](https://argoproj.github.io/argo-events/tutorials/01-introduction/).
    10  
    11  **Q. Can I deploy event-source and sensor in a namespace different than `argo-events`?**
    12  
    13  **A**. Yes. If you want to deploy the event-source in a different namespace than `argo-events`, please update the event-source definition
    14  with the desired namespace and service account. Make sure to grant the service account the [necessary roles](https://github.com/argoproj/argo-events/blob/master/manifests/namespace-install.yaml).
    15  
    16  **Q. How to debug Argo-Events.**
    17  
    18  **A**.
    19  
    20  1. Make sure you have installed everything as instructed [here](https://argoproj.github.io/argo-events/installation/).
    21  1. Make sure you have the `EventBus` resource created within the namespace.
    22  1. The event-bus, event-source and sensor pods must be running. If you see any issue with the pods, check the logs
    23     for sensor-controller, event-source-controller and event-bus-controller.
    24  1. If event-source and sensor pods are running, but you are not receiving any events:
    25       * Make sure you have configured the event source correctly.
    26       * Check the event-source pod's containers logs.
    27  
    28  Note: You can set the environment variable `DEBUG_LOG:true` in any of the containers to output debug logs. See [here](https://github.com/argoproj/argo-events/blob/master/examples/sensors/log-debug.yaml) for a debug example.
    29  
    30  **Q. The event-source pod is receiving events but nothing happens.**
    31  
    32  **A**.
    33  
    34  1. Check the sensor resource is deployed and a pod is running for the resource.
    35  If the sensor pod is running, check for `Started to subscribe events for triggers` in the logs.
    36  If the sensor has subscribed to the event-bus but is unable to create the trigger resource, please raise an issue on GitHub.
    37  
    38  2. The sensor's dependencies have a specific eventSourceName and eventName that should match the values defined in the `EventSource` resource. See full details [here](https://github.com/argoproj/argo-events/blob/master/docs/eventsources/naming.md).
    39  
    40  **Q. Helm chart installation does not work.**
    41  
    42  **A.** The Helm chart for argo events is maintained by the community and can be out of sync with latest release version.
    43  The official installation file is available [here](https://raw.githubusercontent.com/argoproj/argo-events/stable/manifests/install.yaml).
    44  If you notice the Helm chart is outdated, we encourage you to contribute to the [argo-helm](https://github.com/argoproj/argo-helm) repository on GitHub.
    45  
    46  **Q. Kustomization file doesn't have a `X` resource.**
    47  
    48  **A.** The kustomization.yaml file is maintained by the community. If you notice that it is out of sync with the official installation file, please
    49  raise a PR.
    50  
    51  **Q. Can I use the Minio event-source for AWS S3 notifications?**
    52  
    53  **A.** No. The Minio event-source is exclusively for use only with Minio servers. If you want to trigger workloads on an AWS S3 bucket notification,
    54  set up the AWS SNS event-source.
    55  
    56  **Q. If I have multiple event dependencies and triggers in a single sensor, can I execute a specific trigger upon a specific event?**  
    57  
    58  **A.** Yes, this functionality is offered by the sensor event resolution circuitry. Please take a look at the [Circuit and Switch](https://argoproj.github.io/argo-events/tutorials/06-circuit-and-switch/) tutorial.
    59  
    60  **Q. The latest image tag does not point to latest release tag?**
    61  
    62  **A.** When it comes to image tags, the golden rule is _do not trust the latest tag_. Always use the pinned version of the images.
    63     We will try to keep the `latest` tag in sync with the most recently released version.
    64  
    65  **Q. Where can I find the event structure for a particular event-source?**
    66  
    67  **A.** Please refer to [this file](https://github.com/argoproj/argo-events/blob/master/pkg/apis/eventsource/v1alpha1/types.go) to understand the structure
    68  of different types of events dispatched by the event-source pod.