Produce YARP container images

[benjaminpetit]

YARP is a reverse proxy toolkit for building fast proxy servers in .NET using the infrastructure from ASP.NET and .NET. (https://github.com/microsoft/reverse-proxy/)

In a lot of typical Aspire use cases, the user deploys a reverse proxy. This YARP container could be used directly instead of adding manually a new project referencing YARP.

This container could also be used by developers wanting to try YARP directly, without needing to create and compile a new project.

The name of the container should be "reverse-proxy"

Support policy

Since it should be used as an appliance, only the last version of the released container will be supported. We might revisit this policy if we do a major release of YARP that have breaking change in the future.

Issues related to this container should be open on https://github.com/microsoft/reverse-proxy/

Release process

We do not follow the .NET standard way for releasing new products. When we need to push a security fix, we publish a new release as soon as possible, depending on the severity and possible security embargo.

For the container side we expect to release as the same cadence as other containers.

Supported OSes

Since we expect this to be used as an appliance, we will use Azure Linux distroless.

Repo name

reverse-proxy

Desired tags

Currently we don't follow .NET versions. Latest stable is 2.2.0.

2.3-preview1, 2.3-preview. 2-preview, latest

[akoken]

IMHO, it's not a good idea to add a generic docker image for it. YARP is very basic and powerful reverse proxy skeleton. It's fully customizable and you can add so many features on top of it such as authentication, authorization, logging, tracing, metrics, direct forwarding, custom middlewares etc. Yes, you can set some of these features in configuration file, but you need to touch the code at some point.

[lbussell]

[Triage] I've assigned this issue to you @benjaminpetit. I'll document some more detailed instructions for adding images to this repo this week.