Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: tutorial-introduce typo fix #880

Merged
merged 3 commits into from
Sep 14, 2020
Merged

fix: tutorial-introduce typo fix #880

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
98e1e5c
fix: tutorial-introduce typo fix
2044smile Sep 13, 2020
7d25a6a
fix: Troubleshoot msg
2044smile Sep 13, 2020
61c8e97
fix: minor
2044smile Sep 14, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 4 additions & 7 deletions docs/tutorials/01-introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,20 +81,17 @@ from event context or data and pass it to the workflow as arguments.

If you don't see the event-source and sensor pod in `argo-events` namespace,

1. Make sure the correct Role and RoleBindings are applied to the service account
1. Inspect the event-source
2. Make sure the correct Role and RoleBindings are applied to the service account
and there are no errors in both event-source and sensor controller.
2. Make sure the sensor controller configmap has `namespace` set to
`argo-events`.
3. Check the logs of event-source and sensor controller. Make sure the controllers
have processed the event-source and sensor objects and there are no errors.
4. Look for any error in event-source or sensor pod.
5. Inspect the event-source,

kubectl -n argo-events event-source-object-name -o yaml
kubectl -n argo-events get eventsource event-source-object-name -o yaml
2044smile marked this conversation as resolved.
Show resolved Hide resolved

Inspect the sensor,

kubectl -n argo-events sensor-object-name -o yaml
kubectl -n argo-events get sensor sensor-object-name -o yaml

and look for any errors within the `Status`.

Expand Down