konveyor / konveyor/agentic-controller
Research + wire up full operator-install agentic deploy-and-Ready e2e
- Dominant language
- Go
- Stars
- 2
- Forks
- 12
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 41
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:
1. Agent Sandbox v0.5.x installed first (the controller crash-loops without the `sandboxes.agents.x-k8s.io` CRD) — reuse `hack/start-kind.sh`'s Helm install.
2. `OPERATOR_REF` in `hack/install-konveyor.sh` bumped to the merged operator commit.
3. The applied `Tackle` CR set to `agentic_enabled: true`.
4. 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_REF` needs the operator PR's merge commit, so this lands after #591 merges.
Related: konveyor/operator#591
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
- Tech stack
- github-actions, helm, kubernetes
- Domain
- ci-cd, devops, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100