kafbat/kafka-ui

Infra: Move main-tagged images to a separate package

Open

#785 opened on Jan 15, 2025

View on GitHubContributor guide
 (4 comments) (0 reactions) (1 assignee)TypeScript (363 forks)auto 404
good first issuescope/infrastatus/triage/completedtype/enhancement

Repository metrics

Stars
 (2,554 stars)
PR merge metrics
 (PR metrics pending)

Description

To reduce clutter in packages:

  • release images must be kept as is, snapshots (pushes to main) should be published in a separate package (ECR and GHCR, but not docker hub), like kafbat/kafka-ui-rc (rc for release candidate, naming discussable)
  • RC images should be named as a short commit sha rather than a long one as they are at the moment - done in #581
  • after implementing the issue, let's cleanup old RC builds from the main package

Contributor guide

Research direction
Explore the CI/CD workflows to understand how Docker images are currently built and pushed to different registries. Look for references to the `kafka ui` package and tagging strategy. Check the GitHub Packages page for existing snapshot images. Then identify how to set up a new package for main tagged snapshots, update the push steps to target ECR and GHCR (not Docker Hub), and plan cleanup of old RC builds. Validate changes on a branch or fork before opening a PR.
Tech stack
docker
Domain
devopsinfrastructureci cd
Issue type
DevOps
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.
Half day
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
GitDockerGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30