mirror of
https://github.com/jackyzha0/quartz.git
synced 2025-12-24 21:34:06 -06:00
Automated commit at Wed Jun 12 11:30:00 CEST 2024
This commit is contained in:
parent
57a09a3b8d
commit
e7731ee7b8
6
content/AKS supports WASM out of the box.md
Normal file
6
content/AKS supports WASM out of the box.md
Normal file
@ -0,0 +1,6 @@
|
||||
# AKS supports WASM out of the box
|
||||
|
||||
#research
|
||||
|
||||
Investigate this further.
|
||||
|
||||
8
content/Pods will run WASM binaries, not containers.md
Normal file
8
content/Pods will run WASM binaries, not containers.md
Normal file
@ -0,0 +1,8 @@
|
||||
# Pods will run WASM binaries, not containers
|
||||
|
||||
#publish
|
||||
|
||||
When configuring a RuntimeClass on a deployment, the only difference is that the pods are running WASM applications instead of containers.
|
||||
|
||||
From the outside nothing appears to be different.
|
||||
|
||||
7
content/Sidecars become useless when running WASM.md
Normal file
7
content/Sidecars become useless when running WASM.md
Normal file
@ -0,0 +1,7 @@
|
||||
# Sidecars become useless when running WASM
|
||||
|
||||
#publish
|
||||
|
||||
|
||||
Because you cannot mix containers and WASM in the same pod, you can't run sidecar containers on WASM applications in Kubernetes. This makes service meshes that rely on sidecars like Istio useless.
|
||||
|
||||
6
content/WASM.md
Normal file
6
content/WASM.md
Normal file
@ -0,0 +1,6 @@
|
||||
# WASM
|
||||
#research
|
||||
|
||||
- [[Pods will run WASM binaries, not containers]]
|
||||
- [[AKS supports WASM out of the box]]
|
||||
|
||||
@ -32,6 +32,7 @@ If you wish to get in touch with me, take a look at https://mischavandenburg.com
|
||||
* Tech
|
||||
* [[Kubernetes]]
|
||||
* [[Containers]]
|
||||
* [[WASM]]
|
||||
* [[Consultancy]]
|
||||
* [[Infrastructure as Code]]
|
||||
* [[Software Development]]
|
||||
|
||||
Loading…
Reference in New Issue
Block a user