Add Reverse Proxy (YARP) repo to the nightly branch

[benjaminpetit]

Creating a new repo tasks

1. • Create an issue for adding the new repo to the nightly branch.
     It should contain the contents of this checklist as well as the contents of the
     New Image Release checklist.
2. • Create a PR to add new repo and images to the nightly branch.
     Follow the New Image Release
     checklist. The PR must include:
   1. • Unit tests.
   2. • Scenario tests.
   3. • README content. This content will show up on
        GitHub (example),
        MAR, (example), and
        DockerHub (example).
        It should contain:
        • An "About" section explaining what the image is and why it's useful.
        • A "Usage" section explaining the very basics for getting started with the image.
        • Links to official documentation and examples.
        • Links to official support policy.
3. • Create a PR to add the new repo to the MCR repo. https://github.com/microsoft/mcr/pull/3796
4. • Merge the PR to the nightly branch
5. • Create an issue for moving the new repo from the nightly to main branch according to
     the guidelines that were decided on above.

Nightly Branch Tasks

1. • Update Dockerfiles and manifests
   1. • Create Dockerfiles under
        /src/$product/$major-minor-version/$os/$arch/. These Dockerfiles can contain placeholder
        content, as they will be re-generated by templates later.
   2. • If necessary, create new templates for Dockerfiles
        and Readmes
        • See CONTRIBUTING.md
          for instructions on editing templates.
   3. • Update the MAR tags metadata templates
        to include the new images
   4. • Update manifest.json
        to reference the new set of Dockerfiles and templates with the appropriate tags.
        • See the supported tags policy
          to see which tagging patterns to follow.
   5. • Run the commands to generate the Dockerfiles and READMEs based on templates:
      1. • pwsh .\eng\readme-templates\Get-GeneratedDockerfiles.ps1
      2. • pwsh .\eng\readme-templates\Get-GeneratedReadmes.ps1
      3. • Inspect generated changes for correctness
2. • Update tests
   1. • Add new image to TestData.cs
   2. • Add unit tests and scenario tests. Follow existing patterns for other images.
3. • Consider authoring sample Dockerfiles and adding them to samples
   1. • If not adding sample Dockerfiles, provide justification: samples will live in the reverse-proxy and aspire repo
4. • Run build-and-test.ps1 to build and test your images
     • See CONTRIBUTING.md for more detailed instructions
5. • Commit changes
6. • Create PR
7. • Consider drafting an announcement to be posted on this repo's discussions page
     when images are published
8. • Get PR signoff
9. • Merge PR to nightly branch
10. • Wait for automatically queued CI build to finish on dotnet-docker-nightly pipeline (internal MSFT link)
11. • Confirm READMEs have been updated on MAR and Docker Hub

[lbussell]

OK, the images have been published to the nightly repo:

docker pull mcr.microsoft.com/dotnet/nightly/reverse-proxy:2.3-preview

@benjaminpetit, what we're looking for now is:

• Criteria/timeline for moving YARP images to the main branch. For example, with 2.3 GA? Or whenever 2.3 has a stable preview release?
• Some plan for announcing the availability of these images / asking for community feedback. We can coordinate on this offline.

Related: dotnet/yarp#2525