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
The runtime-class-manager is the spiritual successor to the kwasm-operator. kwasm has been developed as an experimental, simple way to install Wasm runtimes. This experiment has been relatively successful, as more and more users utilized it to fiddle around with Wasm on Kubernetes. However, the kwasm-operator has some limitations that make it difficult to use in production. The runtime-class-manager is an attempt to address these limitations to make it a reliable and secure way to deploy arbitrary containerd shims.
6
6
@@ -12,16 +12,16 @@ The name should be treated as a working title and is hopefully subject to change
12
12
13
13
For the 1.0 release of runtime-class-manager, we consider three milestones:
14
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.
-**M1: [RCM MVP for Spinkube](https://github.com/spinframework/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/spinframework/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)**
19
+
-**M3: [Full implementation of the initial spec](https://github.com/spinframework/runtime-class-manager/milestone/3)**
20
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
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
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
25
25
26
26
## Usage
27
27
@@ -33,8 +33,8 @@ Stable spec of the Shim CRD based on the [initial proposal](https://hackmd.io/Tw
33
33
make docker-build docker-push IMG=<some-registry>/runtime-class-manager:tag
34
34
```
35
35
36
-
**NOTE:** This image ought to be published in the personal registry you specified.
37
-
And it is required to have access to pull the image from the working environment.
36
+
**NOTE:** This image ought to be published in the personal registry you specified.
37
+
And it is required to have access to pull the image from the working environment.
38
38
Make sure you have the proper permission to the registry if the above commands don’t work.
39
39
40
40
**Install the CRDs into the cluster:**
@@ -49,7 +49,7 @@ make install
49
49
make deploy IMG=<some-registry>/runtime-class-manager:tag
50
50
```
51
51
52
-
> **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin
52
+
> **NOTE**: If you encounter RBAC errors, you may need to grant yourself cluster-admin
0 commit comments