konveyor / konveyor/agentic-controller

Epic: clean up stale and broken agent/workflow runs (TTL GC, fail-fast on broken pods, console cleanup)

Open
#201 3 comments 0 reactions 1 assignee Claimed by @ibolton336 View on GitHub
enhancement stream/controller
Dominant language
Go
Stars
2
Forks
12
Avg merge
2d 5h
Merged PRs (30d)
41

Description

## Summary

Tracking thread for cleaning up **stale and broken agent/workflow runs** — both
the automatic controller-side lifecycle (TTL GC, fail-fast on broken pods,
resource cascade) and the interactive console-side cleanup (bulk delete, find
broken runs).

Today terminal runs accumulate forever, and runs whose pods are stuck on error
conditions (`ImagePullBackOff`, `CrashLoopBackOff`, unschedulable, config
errors) hang indefinitely with no expiry — leaving clutter in `kubectl`, the
console, and the cluster.

This is distinct from the existing *reporting* work (#171 surface failures to
status, #189 termination-log JSON, #187 SkillCard image verification), which
tells you *why* a run failed. This thread is about *reaping* what's left.

## Controller (konveyor/agentic-controller)

- [x] #198 — TTL-based garbage collection for terminal AgentRuns / AgentWorkflowRuns
- [x] #199 — Fail-fast and reap runs whose pods are stuck on error conditions
- [ ] #200 — Owner-reference cascade + orphan sweep on deletion

## Console (konveyor/tackle2-ui)

- [ ] konveyor/tackle2-ui#3556 — Bulk-delete / clear-completed for stale runs
- [ ] konveyor/tackle2-ui#3557 — Surface pod error conditions + filter for broken runs

## Related (not part of this thread)

- #171, #189, #187, #130, #166

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.