Use WASI microservices on AKS with wasmCloud
As a substitute for SpinKube, you should use one other CNCF mission, wasmCloud. Right here you want a Helm chart to put in the varied wasmCloud parts on the identical time. This requires having the Azure CLI and kubectl handle AKS, as there’s no integration with the Azure Portal. On the identical time, as there’s fairly a distinct architectural strategy, you should 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 begin a wasmCloud occasion after which deploy the parts that make up your utility. WasmCloud has its personal command-line administration instrument, and you should ahead site visitors to the administration pod to make use of it.
Once more, you should 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 should use the command-line instrument to deploy and run the applying. WasmCloud is designed to assist a part mannequin for constructing and working purposes, with the intent of delivering a normal method of describing and calling WASI parts, with assist from Cosmonic.