Research + wire up full operator-install agentic deploy-and-Ready e2e
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Compare konveyor/operator's llm-proxy-test.yml with hack/start-kind.sh and hack/install-konveyor.sh to determine whether this e2e belongs in the operator or agentic-controller repository. After operator#591 merges, use the existing Agent Sandbox Helm install, the merged OPERATOR_REF, and an agentic_enabled Tackle resource. Done means the full install completes and the agentic-controller Deployment reaches Ready.
Written by the indexing model from the issue text.
Description
Summary
Research and determine where the operator-install + full agentic deploy-and-Ready e2e should live, then wire it up. This is the "does the whole stack install and reach Ready" test that proves konveyor/operator#591 end-to-end.
Background
konveyor/operator#591 lands the operator plumbing for the agentic controller as an opt-in operand (spec.agentic_enabled, vendored CRDs/RBAC, a Deployment template, CSV/bundle wiring). That PR deliberately does not include agentic runtime e2e — the operator-PR gates are ansible-lint + bundle-sync-check + the existing global-ci install (with agentic off).
The full deploy-and-Ready path needs:
- Agent Sandbox v0.5.x installed first (the controller crash-loops without the
sandboxes.agents.x-k8s.ioCRD) — reusehack/start-kind.sh's Helm install. OPERATOR_REFinhack/install-konveyor.shbumped to the merged operator commit.- The applied
TackleCR set toagentic_enabled: true. - Wait for the agentic-controller Deployment to reach Ready.
Open question (the "research/determine" part)
Should this e2e live in konveyor/operator (mirroring llm-proxy-test.yml) or grow here in agentic-controller (extending hack/install-konveyor.sh + a workflow)? Determine ownership, then implement.
Notes
- Not targeted for the 0.11 timeframe. Does not gate konveyor/operator#591.
- Chicken-and-egg: bumping
OPERATOR_REFneeds the operator PR's merge commit, so this lands after #591 merges.
Related: konveyor/operator#591
- 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
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
masahitojp/mariamem#108 ·
Maintainers usually reply within 1 day
-
[Bug] Pod detail shows CPU usage ten times too high, and throws on decimal memory suffixesPossibly taken @RaphaelFakhri claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 11 days
-
tsuru_app_cname and tsuru_app_router don't handle removal outside terraformPossibly taken @lbarrosby claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
contributor-friendly good-first-issue lang:go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
irbis-sh/zen-desktop#870 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day