deploy/kubernetes: reconcile Agent Service Flow CRDs to runnable workloads
Open
Nobody has claimed this yet.
codex
enhancement
- Dominant language
- Go
- Stars
- 23.1k
- Forks
- 2.4k
- Avg merge
- 1h 7m
- Merged PRs (30d)
- 23
Description
Goal
Turn the alpha Kubernetes CRDs into a minimally runnable deployment path so teams can deploy services, agents, and flows through one native Kubernetes lifecycle.
Scope
- Add an opt-in controller/reconciler skeleton for Agent, Service, and Flow resources.
- Reconcile each resource into a Deployment/Service shape wired with labels/status conditions.
- Keep generated manifests and controller behavior additive and alpha.
- Include envtest/fake-client style tests or narrow unit tests for reconcile output.
Acceptance criteria
- Applying an Agent, Service, or Flow custom resource produces the expected workload spec in tests.
- Status conditions expose ready/error state for the inner-loop/deploy story.
- go test ./deploy/kubernetes/... passes.
Contributor 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.
Research direction
Start in deploy/kubernetes and run go test ./deploy/kubernetes/... to understand the existing alpha CRDs and test coverage. Add the opt-in reconciliation path for Agent, Service, and Flow resources, then verify that tests produce the expected workload specs and ready/error status conditions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- distributed-systems, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100