Scaling protection — maxConcurrentRuns
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
Research direction
Start by reading ADR 0006 and locating the AgentRun controller reconciliation path in this repository. Trace how running and Pending AgentRuns are counted and how terminal transitions trigger reconciliation; issue #65 provides the cancellation context. Done means configurable global or per-namespace limits, FIFO queuing without rejection, and tests covering slot release and pending cancellation.
Written by the indexing model from the issue text.
Description
Add a configurable limit on concurrent AgentRuns to prevent cluster resource exhaustion.
Design (per ADR 0006)
- Configurable
maxConcurrentRunson the controller (global and/or per-namespace) - Runs beyond the limit remain in
Pendingphase until a slot opens (queue, not reject) - Kubernetes
ResourceQuotaremains the primary hard protection against resource exhaustion;maxConcurrentRunsprovides a better UX (runs queue rather than fail)
Controller behavior
- Before creating a Sandbox, the controller counts running AgentRuns
- If at or above the limit, the run stays in
Pending - When a running AgentRun reaches terminal state, the controller picks the next
Pendingrun (FIFO) - Pending runs can still be cancelled (see #65)
Future
- Kueue integration for sophisticated multi-tenant quota management (per-namespace, per-team, borrowing/preemption) is the long-term path if needed
References
- ADR 0006: Hub addon pattern for agent resources
- Enhancement: konveyor/enhancements#295 — Scaling protection 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 1 day ago. Openenhancement stream/controller
konveyor/agentic-controller#304 · 1 assignee ·
Maintainers usually reply within 1 day
All issues in konveyor/agentic-controller
Similar issues
-
ai-driven-fuzzing bug Minor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
linagora/cozy-stack#5162 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
prometheus/prometheus-mcp#213 ·
Maintainers usually reply within 3 days
-
Deleting a client-role keycloak_generic_role_mapper removes all roles of that client from the scope mappingPossibly taken @albarkauss claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
keycloak/terraform-provider-keycloak#1786 ·
Maintainers usually reply within 5 days
-
mqtt_paho: transformer.DeleteExtension and DeleteAttribute make WritePubMessage failPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
cloudevents/sdk-go#1349 ·
-
getChaosHub always returns totalFaults "0"Possibly taken @Aryanbhargava18 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
litmuschaos/litmus#5710 ·
Maintainers usually reply within 3 days