Skip to content

docs(*): misc updates#563

Open
vdice wants to merge 1 commit intospinframework:mainfrom
vdice:docs/misc-updates
Open

docs(*): misc updates#563
vdice wants to merge 1 commit intospinframework:mainfrom
vdice:docs/misc-updates

Conversation

@vdice
Copy link
Collaborator

@vdice vdice commented Feb 5, 2026

Describe your changes

Some minimal README and doc updates in preparation for RCM going "prime time" as the default wasm/runtimeclass installer for SpinKube (ref spinframework/spinkube-docs#339)

@vdice vdice force-pushed the docs/misc-updates branch 2 times, most recently from cde7475 to 9153d09 Compare February 5, 2026 23:57
Signed-off-by: Vaughn Dice <vdice@akamai.com>
@vdice vdice force-pushed the docs/misc-updates branch from 9153d09 to 51d3255 Compare February 6, 2026 21:00
* `spec.runtimeClass.name`: Name of the Kubernetes RuntimeClass
- This name should match what is expected by shim-specific operator(s) on the cluster
- For example, the [Spin Operator](https://github.com/spinframework/spin-operator) utilizes a [SpinAppExecutor](https://www.spinkube.dev/docs/reference/spin-app-executor/) resource
to run Spin Apps; the default RuntimeClass name it expects can be seen [here](https://github.com/spinframework/spin-operator/blob/main/config/samples/spin-shim-executor.yaml)
Copy link
Contributor

@Shunpoco Shunpoco Feb 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO: Can we describe a generated runtime class has Scheduling.NodeSelector which derived from Shim CR's spec.nodeSelector (in this doc or shim.md)? I think the Scheduling is very important. If a runtimeclass doesn't have it (by user's mis-modification or else), a Spin pod could be allocated anywhere including a non-spin cluster


- **M1: [RCM MVP for Spinkube](https://github.com/spinframework/runtime-class-manager/milestone/1)**
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.
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. _This is now complete._
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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. _This is now complete._
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. _This is now complete._

@Shunpoco
Copy link
Contributor

Shunpoco commented Feb 7, 2026

@vdice I'm not a reviewer/maintainer of the repository (of course you know!), but let me put small comments above 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants