This roadmap reflects the current direction of the kube-bind project. Items are grouped by theme, not strict release milestones. Track progress via GitHub Issues.
- Pluggable session storage — replace in-memory backend session storage with an external/pluggable implementation, enabling replicas > 1 for HA deployments (#424, #488)
- CRD lifecycle / BoundSchema changes — support schema evolution after initial binding, including updates and versioning (#404)
- Delete flow — full lifecycle support for APIServiceExport deletion and graceful unbinding (#352)
- Backend production hardening — address remaining gaps for production-grade deployments (#284)
- Related resources — support binding of associated resources such as ConfigMaps and Secrets alongside primary CRDs
- Multi-provider/consumer support — allow a single consumer cluster to bind the same CRD from multiple providers, and other multi-tenancy scenarios (#321)
- Object metadata propagation — propagate selected labels/annotations between provider and consumer objects (#315)
- Reduced konnector permissions — tighten RBAC footprint of the konnector agent in consumer clusters (#303)
- UI-only binding flow — allow service binding without CLI, purely via browser/OIDC redirect flow (#406)
- Dry-run support — fix
--dry-runinbind apiservice(#365)
- kcp integration — make the konnector kcp-aware and support serving from APIBindings (#317, #300, #323)
- multicluster-runtime refactor — refactor the konnector to use multicluster-runtime for improved multi-cluster controller patterns (#299)
- PlatformMesh integration — provider-side integration with PlatformMesh (#447)
This roadmap is maintained by the kube-bind maintainers.
Contributions and feedback welcome via
GitHub Discussions or
#kube-bind on Kubernetes Slack.