There’s a new first-class API called WasmPlugin that lets you configure which plugins to install, where to fetch them (an OCI image, container-local file, or remote HTTP resource), where to install them (via a Workload selector ), and a configuration struct to pass in to plugin instances. What to expect: a new plugin configuration API and a reliable fetching and installation mechanism We think this will enable a whole new direction for Istio. At Tetrate, we believe this technology is maturing quickly and therefore we have been investing in upstream Istio to make the configuration API, distribution mechanism, and extensibility experience starting from Go easier. Wasm promises to make the mesh and gateways easily extensible by developers. This post will cover the basics of Wasm in Istio and why it matters followed by a short tutorial on building your own Wasm plugin and deploying it to the mesh. Tetrate engineers Takeshi Yoneda and Lizan Zhou have been instrumental in making this happen. Three years in the making, Istio now has a powerful extension mechanism for adding custom and third-party Wasm modules to sidecars in the mesh. New WebAssembly infrastructure in Istio makes it easy to inject additional functionality into mesh deployments
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |