Skip to content

Commit 6de4fcb

Browse files
authored
Add roadmap to README.md (#82)
* add roadmap to README.md * add ideas to roadmap
1 parent 3929f4d commit 6de4fcb

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

README.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,18 @@ The name should be treated as a working title and is hopefully subject to change
1010

1111
## Roadmap
1212

13-
- tbd
13+
For the 1.0 release of runtime-class-manager, we consider three milestones:
14+
15+
- **M1: [RCM MVP for Spinkube](https://github.com/spinkube/runtime-class-manager/milestone/1)**
16+
This milestone is about getting RCM to a state where Spinkube can rely on RCM and use it as a dependency instead of Kwasm. This means, that the focus is on managing lifecycle of [containerd-shim-spin](https://github.com/spinkube/containerd-shim-spin) on nodes.
17+
- **M2: [Kwasm Feature Parity](https://github.com/spinkube/runtime-class-manager/milestone/2)**
18+
All shims that kwasm can install, should be installable via rcm. Automated tests are in place to ensure installation of RCM and shims that are supported by Kwasm.
19+
- **M3: [Full implementation of the initial spec](https://github.com/spinkube/runtime-class-manager/milestone/3)**
20+
Stable spec of the Shim CRD based on the [initial proposal](https://hackmd.io/TwC8Fc8wTCKdoWlgNOqTgA). After 1.0 we assume no breaking changes of the Shim CRD. Arbitrary shims can be installed via RCM and prominent shims are tested automatically, on various Kubernetes distributions.
21+
- Future (ideas):
22+
- support for additional container runtimes, like CRI-O to enable RCM on OpenShift
23+
- alternative shim installation via Daemonset instead of Jobs
24+
- treating node-installer as a daemon process, to enable better conflict resolution
1425

1526
## Usage
1627

0 commit comments

Comments
 (0)