Use WASI microservices on AKS with wasmCloud
As a substitute for SpinKube, you need to use one other CNCF venture, wasmCloud. Right here you want a Helm chart to put in the varied wasmCloud parts on the similar time. This requires having the Azure CLI and kubectl handle AKS, as there’s no integration with the Azure Portal. On the similar time, as there’s fairly a distinct architectural method, you have to begin from scratch, rearchitecting your cluster and utility to be used with wasmCloud.
Begin by making a Kubernetes namespace for wasmCloud, earlier than utilizing Helm to put in the wasmCloud platform parts. As soon as the pods have restarted, use kubectl to start out a wasmCloud occasion after which deploy the parts that make up your utility. WasmCloud has its personal command-line administration instrument, and you have to ahead visitors to the administration pod to make use of it.
Once more, you have to use YAML to explain your utility; nonetheless, now you’re utilizing wasmCloud’s personal orchestration instruments, so you’ll use its descriptions of your utility parts. As soon as full, you need to use the command-line instrument to deploy and run the appliance. WasmCloud is designed to assist a element mannequin for constructing and working functions, with the intent of delivering a regular manner of describing and calling WASI parts, with assist from Cosmonic.