envoyproxy / envoyproxy/envoy

Move VRP to being a sandbox (only)

Open
#26,422 4 comments 0 reactions 1 assignee Assigned to @phlax View on GitHub
area/ci area/docker area/examples no stalebot
Dominant language
C++
Stars
28.9k
Forks
5.6k
Avg merge
1d 20h
Merged PRs (30d)
428

Description

Currently we re/build the VRP image/s on every CI run and publish them to dockerhub

This takes up a lot of CI cycles/time

Mostly i think due to lack of documentation, the VRP images dont seem to get a lot of air play

There are other issues with how the images are currently built that cause headaches/workarounds for the sandboxes - where VRP has 2 despite lacking docs

My suggestion is to shift what is currently being built into an image into a sandbox recipe

If someone wants to use the image they can build/customize it quickly from the sandbox where it will have documentation explaining how to build and use it, some of the tools included and ways to make use of them

I think doing this will kill 3 proverbial birds with 1 stone - ie speedup/simplify docker ci/publishing, make the VRP more visible with better docs, and provide a better resolution to the current sandbox workarounds

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.