Problem statement
OpenSRE currently lacks a first-class ArgoCD integration. That makes it harder to investigate rollout failures, configuration drift, sync issues, and deployment health in GitOps-driven Kubernetes environments.
Proposed solution
Add a first-class ArgoCD integration that supports:
- onboarding, authentication, and connectivity verification
- reading application status, sync state, health, revision history, and recent changes
- using ArgoCD evidence during investigation planning and root-cause analysis
- surfacing deployment drift and recent rollout context clearly in reports
Acceptance criteria
- the integration is usable from the investigation workflow end to end
- setup and usage are documented clearly
- the implementation is backed by end-to-end tests in
tests/e2e or equivalent
- the PR includes a screen video showing setup plus a successful investigation flow using ArgoCD
- vibecoding without testing will not be allowed; PRs without working end-to-end coverage and screen-video proof should be rejected
Problem statement
OpenSRE currently lacks a first-class ArgoCD integration. That makes it harder to investigate rollout failures, configuration drift, sync issues, and deployment health in GitOps-driven Kubernetes environments.
Proposed solution
Add a first-class ArgoCD integration that supports:
Acceptance criteria
tests/e2eor equivalent