You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,18 @@ The name should be treated as a working title and is hopefully subject to change
10
10
11
11
## Roadmap
12
12
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.
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
0 commit comments