envoyproxy/envoy

support oci_uri as a remote data source for wasm

Open

#33,212 opened on Mar 29, 2024

View on GitHub
 (15 comments) (17 reactions) (0 assignees)C++ (5,373 forks)batch import
area/wasmenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Title: One line description

Description:

Envoy only supports fetching a WASM module remotely via http

Majority of the WASM Modules now live in OCI Registries, so would be great if an oci field was supported to allow users to fetch WASM modules directly instead of using a shim (an auxiliary control plane creating a temporary file server or a sidecar agent that prefetches from an OCI registry and persists it into the common filesystem) that deals with the CRUD state machine

[optional Relevant Links:]

Any extra documentation required to understand the issue.

Contributor guide

Research direction
Investigate the existing RemoteDataSource implementation in Envoy and the HTTP getter. Study Helm's OCI getter as a reference for implementing an OCI getter in Envoy. Consider authentication, image pulling, and integration with the WASM engine.
Tech stack
cpp
Domain
backendinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C++WASMOCI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30