envoy-actions

Getting Started

Requirements

• System: MacOS, Ubuntu or Windows
• Bazel
• Docker

Installation

Build and run Examples by Github Actions

🎯 Envoy

• build in docker ( Windows，Ubuntu )

• build with bazel (MacOS, Windows, Ubuntu)

• build in sandbox

  • supported：ubuntu
  • 🐳 build on docker image like envoyproxy/envoy-build-ubuntu

🎯 envoy-mobile

Mobile client networking libraries based on the Envoy project.

To build Envoy Mobile, your system must also be set up for building Envoy. To get started, you can use the Github Action Workflows.

Envoy Mobile can build on MacOS, selected macOS for the 3 cpu cores.

The output of Envoy Mobile for each launguage(Android，iOS):

• Java: envoy_android_aar_sources
• Kotlin: envoy_android_aar_sources
• objective-c: envoy_ios_framework
• Swift: envoy_ios_cocoapods

Github Action Workflows

• Android

  • CPU Arch supported: x86, armeabi-v7a, arm64-v8a (Official only x86)

• iOS

  • CPU Arch supported: i386,x86_64,armv7,arm64

• Artifacts

  • The workflow not use the github cache, fully build and upload the sdk and examples.

🎯 envoy-mobile-app

TODO:

Compatible Envoy builds

Envoy is the first host side implementation of Proxy-Wasm ABI, and we run end-to-end tests with multiple versions of Envoy and Envoy-based istio/proxy in order to verify each Proxy-Wasm SDK works as expected.

Please refer to workflows for which version is used for End-to-End tests.

External links

• WebAssembly for Proxies (ABI specification)
• WebAssembly for Proxies (AssemblyScript SDK)
• WebAssembly for Proxies (C++ SDK)
• WebAssembly for Proxies (Rust SDK)
• WebAssembly for Proxies (Zig SDK)