Skip to content

Commit 2c4057b

Browse files
committed
skip for container integration
Signed-off-by: Michelle Dhanani <[email protected]>
1 parent 809bdd8 commit 2c4057b

File tree

1 file changed

+33
-0
lines changed

1 file changed

+33
-0
lines changed
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# SKIP 005 - Container Integration in SpinKube
2+
3+
Summary: Provide a path for running containers alongside WebAssembly workloads in SpinKube.
4+
5+
Owner: Michelle Dhanani <[email protected]>
6+
7+
Impacted Projects:
8+
9+
- [X] spin-operator
10+
- [X] `spin kube` plugin
11+
- [ ] runtime-class-manager
12+
- [X] containerd-shim-spin
13+
- [ ] Governance
14+
- [ ] Creates a new project
15+
16+
Created: October 2, 2024
17+
18+
Updated: October 2, 2024
19+
20+
## Background
21+
22+
There are scenarios where one might want to run a container alongside a WebAssembly application in the same pod. One reason might be a continuty of tooling (service meshes, logs, metrics). Another reason is there is a part of a logical workload that can be WebAssembly but another part that cannot run as WebAssembly and would need to run as a sidecar container in the same Pod and be able to communicate to the WebAssembly bits over localhost.
23+
24+
## Proposal
25+
26+
One option is to add a way to configure containers in the SpinApp CR.
27+
28+
TBD - would like to collect feedback here.
29+
30+
## Alternatives Considered
31+
32+
What else have you considered and why is the proposed solution a better fit?
33+
N/A

0 commit comments

Comments
 (0)