adaptive-enforcement-lab/argo-events-setup-guide
plugins/patterns/skills/argo-events-setup-guide/SKILL.md
Deploy event-driven automation with EventSource, EventBus, and Sensor configuration. Complete setup guide for production Argo Events on Kubernetes clusters.
tools
Updated Mar 27, 2026
$ install --global
skillsauthnpx skillsauth add adaptive-enforcement-lab/claude-skills argo-events-setup-guideInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 29, 2026, 10:48 AM36.4s2 files scanned
SKILL.md
- name:
- argo-events-setup-guide
- description:
- >-
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
- Source Documentation
- AEL Patterns
Related Skills
adaptive-enforcement-lab/workload-identity-federation-implementation
documentation
VerifiedTrustedCommunity
Workload Identity Federation implementation guide. GKE setup, IAM bindings, ServiceAccount configuration, migration from service account keys, and troubleshooting patterns.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/workflow-trigger-security
development
VerifiedTrustedCommunity
Secure GitHub Actions trigger patterns for pull requests, forks, and reusable workflows. Preventing privilege escalation and code injection through trigger misconfiguration.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/third-party-action-risk-assessment
development
VerifiedTrustedCommunity
Structured framework for evaluating GitHub Actions security before adoption. Trust tiers, risk assessment checklist, and decision tree for action evaluation.
SKILL.mdUpdated Mar 27, 2026
adaptive-enforcement-lab/storing-credentials
testing
VerifiedTrustedCommunity
Securely store GitHub App credentials across different environments. GitHub Actions secrets, external CI, Kubernetes, and automated rotation patterns.
SKILL.mdUpdated Mar 27, 2026