Here is the development roadmap for v0.7.0. Contributions and feedback are welcome.

P1: Critical Path Items

• API v1alpha2 Release

  • v1alpha2 CRD & types: Finalize schema and defaulting/validation
  • Compatibility strategy:
    • Dual-version serving (v1alpha1 + v1alpha2) with conversion webhook
    • Test coverage: Add/extend integration/e2e tests for create/update/rollback paths using v1alpha2 manifests

• In-place Update Enhancement

  • Warm-up stage (Phase 2): Support pre-pulled images / pre-warmed models during upgrade phase
  • Warm-up status & observability: Conditions/events for progress, completion, failure, and retry semantics
  • Warm-up examples: Provide at least one end-to-end manifest and walkthrough

• Coordinated Update Improvements

  • Clarify trigger conditions
  • State machine tracking (explicit phases + transitions + reasons)
  • Dependency configuration interactions (ordering/constraints between roles)

• Service Discovery / Configuration

  • Config format cleanup: Reduce redundancy and clarify contract
  • ConfigMap consolidation (if applicable): Merge/simplify configmaps while keeping upgrade safe

• Documentation

  • v0.7.0 API v1alpha2 guide: Concepts + full reference + examples
  • Warm-up guide: Configuration, lifecycle, troubleshooting
  • End-to-End upgrade practices: 0.6.x → 0.7.0 upgrade/migration playbook
  • Coordination update specifications: State machine + failure handling + examples
  • InstanceSet deployment procedures (single-node/multi-node)

• CLI (rbgctl) Enhancement

  • v1alpha2 support: CRUD + status display aligned with new conditions/phases
  • Plugin mechanism Support : With storage, Deployer, model source,AI Evaluator
  • Model Lifecycle management improvements