Use WASI microservices on AKS with wasmCloud
As a substitute for SpinKube, you need to use one other CNCF undertaking, wasmCloud. Right here you want a Helm chart to put in the varied wasmCloud elements 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 may be fairly a special architectural strategy, you must begin from scratch, rearchitecting your cluster and software to be used with wasmCloud.
Begin by making a Kubernetes namespace for wasmCloud, earlier than utilizing Helm to put in the wasmCloud platform elements. As soon as the pods have restarted, use kubectl to start out a wasmCloud occasion after which deploy the elements that make up your software. WasmCloud has its personal command-line administration instrument, and you must ahead site visitors to the administration pod to make use of it.
Once more, you should use YAML to explain your software; nonetheless, now you’re utilizing wasmCloud’s personal orchestration instruments, so you’ll use its descriptions of your software elements. As soon as full, you need to use the command-line instrument to deploy and run the appliance. WasmCloud is designed to help a part mannequin for constructing and operating purposes, with the intent of delivering a regular method of describing and calling WASI elements, with help from Cosmonic.
