Cancel semantics for AgentRun and AgentWorkflowRun
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 52/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- api, infrastructure
Research direction
Start by reading ADR 0006, then locate the AgentRun and AgentWorkflowRun resource definitions and their controllers. Trace the Hub cancel handler and the pending and running controller paths. Done means cancel requests revoke the Hub API token, set spec.cancel, produce the Cancelled phase, avoid creating pending Sandboxes, delete running Sandboxes, and clean up tokens and Secrets idempotently.
Written by the indexing model from the issue text.
Description
Add cancellation support for AgentRun and AgentWorkflowRun.
Design (per ADR 0006)
- Add
spec.cancelfield to AgentRun and AgentWorkflowRun - Add
Cancelledphase to AgentRunPhase - Controller behavior on
spec.cancel: true:- Running: delete the Sandbox, set phase to
Cancelled - Pending (queued behind
maxConcurrentRuns): no Sandbox exists; set phase toCancelledimmediately, preventing Sandbox creation
- Running: delete the Sandbox, set phase to
- Token and Secret cleanup is idempotent in both cases
Hub side
- Hub cancel handler (
POST /hub/agent/runs/:name/cancel): revokes the Hub API token, then setsspec.cancel: trueon the CR - The UI cancels runs (never deletes them)
References
- ADR 0006: Hub addon pattern for agent resources
- Enhancement: konveyor/enhancements#295 — Hub integration section
- Dominant language
- Go
- Stars
- 5
- Forks
- 13
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 27
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from konveyor/agentic-controller
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konveyor/agentic-controller#305 ·
Maintainers usually reply within 1 day
-
bug stream/controller
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
konveyor/agentic-controller#164 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
konveyor/agentic-controller#124 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
konveyor/agentic-controller#323 ·
Maintainers usually reply within 1 day
-
Provider-aware Gateway verification for aws-bedrock / gcp-vertex-ai, so bad credentials fail at verify rather than mid-runPossibly taken @ibolton336 claimed this 2 days ago. Openenhancement stream/controller
konveyor/agentic-controller#304 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in konveyor/agentic-controller
Similar issues
-
component:obi contribfest go test
Difficulty 2/5 Under an hour Newbie friendliness 83/100
open-telemetry/opentelemetry-ebpf-instrumentation#4143 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area/ambient
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
kubernetes-sigs/kueue#18324 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 84/100