envoyproxy/envoy

Publish images to GHCR

Open

#45083 opened on May 15, 2026

View on GitHub
 (7 comments) (0 reactions) (0 assignees)C++ (27,997 stars) (5,373 forks)batch import
area/dockerarea/releaseenhancementhelp wanted

Description

Title: Publish envoy images to GHCR

Description:

Would it be possible to publish envoy images to Github container registry?

Contributor guide

Tech stack
dockergithub actions
Domain
devopsci cd
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.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Docker knowledgeGitHub Actions basicsUnderstanding of Envoy's release process
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Examine the current CI/CD pipeline, specifically how Envoy images are built and pushed to Docker Hub. Look at the GitHub Actions workflows in .github/workflows for any existing container image publishing steps. Determine if there is a dedicated release workflow or if images are built on pushes to certain branches. Check if there are any discussions or comments in the issue about authentication or naming conventions for GHCR. The goal is to create a new workflow or extend an existing one to also push to ghcr.io/envoyproxy/envoy.