Agent skill
argo-events-setup-guide
Deploy event-driven automation with EventSource, EventBus, and Sensor configuration. Complete setup guide for production Argo Events on Kubernetes clusters.
Install this agent skill to your Project
npx add-skill https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/argo-events-setup-guide
SKILL.md
Argo Events Setup Guide
When to Use This Skill
This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation.
Implementation
This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation.
Components
| Component | Purpose | Guide |
|---|---|---|
| EventSource | Connect to external systems (Pub/Sub, webhooks) | EventSource Configuration |
| EventBus | Message broker for event delivery | EventBus Configuration |
| Sensor | Filter events and trigger workflows | Sensor Configuration |
Quick Start
- Deploy EventBus - Start with JetStream for production
- Configure EventSource - Connect your Pub/Sub topic or GitHub webhooks
- Create Sensor - Define event filters and triggers
EventBus First
Deploy the EventBus before creating EventSources or Sensors. Without a running EventBus, events have nowhere to go.
Troubleshooting
Events Not Arriving
- Check EventSource logs:
kubectl logs -n argo-events -l eventsource-name=<name> - Verify Pub/Sub subscription exists in GCP console
- Confirm service account has
pubsub.subscriberrole
Events Arriving But Not Triggering
- Check Sensor logs:
kubectl logs -n argo-events -l sensor-name=<name> - Verify filter conditions match event payload
- Test with a simple sensor that logs all events
Events Lost During Restarts
- Enable persistence on EventBus
- Increase
maxAgeretention - Monitor EventBus storage usage
Related
- Argo Workflows Patterns - WorkflowTemplate design and error handling
- ConfigMap as Cache Pattern - Volume mounts for zero-API reads
- Event-Driven Deployments - The journey to zero-latency automation
Components
| Component | Purpose | Guide |
|---|---|---|
| EventSource | Connect to external systems (Pub/Sub, webhooks) | EventSource Configuration |
| EventBus | Message broker for event delivery | EventBus Configuration |
| Sensor | Filter events and trigger workflows | Sensor Configuration |
Quick Start
- Deploy EventBus - Start with JetStream for production
- Configure EventSource - Connect your Pub/Sub topic or GitHub webhooks
- Create Sensor - Define event filters and triggers
EventBus First
Deploy the EventBus before creating EventSources or Sensors. Without a running EventBus, events have nowhere to go.
Troubleshooting
Events Not Arriving
- Check EventSource logs:
kubectl logs -n argo-events -l eventsource-name=<name> - Verify Pub/Sub subscription exists in GCP console
- Confirm service account has
pubsub.subscriberrole
Events Arriving But Not Triggering
- Check Sensor logs:
kubectl logs -n argo-events -l sensor-name=<name> - Verify filter conditions match event payload
- Test with a simple sensor that logs all events
Events Lost During Restarts
- Enable persistence on EventBus
- Increase
maxAgeretention - Monitor EventBus storage usage
Related
- Argo Workflows Patterns - WorkflowTemplate design and error handling
- ConfigMap as Cache Pattern - Volume mounts for zero-API reads
- Event-Driven Deployments - The journey to zero-latency automation
Troubleshooting
See troubleshooting.md for common issues and solutions.
Related Patterns
- Argo Workflows Patterns
- ConfigMap as Cache Pattern
- Event-Driven Deployments
References
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
github-token-permissions-overview
Understanding GITHUB_TOKEN scope, default permissions, and implementing least-privilege principle for GitHub Actions workflows.
secure
Find and fix security issues before they become incidents. Vulnerability scanning, SBOM generation, supply chain security, and secure authentication workflows.
complete-workflow-examples
Copy-paste hardened CI/CD workflows with SHA-pinned actions, minimal GITHUB_TOKEN permissions, OIDC authentication, and comprehensive security scanning for GitHub Actions.
ephemeral-runner-patterns
Disposable runner patterns for GitHub Actions. Container-based, VM-based, and ARC deployment strategies with complete state isolation between jobs.
action-pinning-overview
Why pinning GitHub Actions to SHA-256 commits matters for supply chain security. Attack vectors from unpinned actions and comparison of tag vs SHA pinning.
github-actions-security-patterns-hub
Complete security patterns for GitHub Actions covering action pinning, GITHUB_TOKEN permissions, third-party action risks, secret management, and runner security.
Didn't find tool you were looking for?