Working on a registry control plane
Why I am building a registry control plane on top of registry:2, and why it stayed private until it saw real use.
I am currently building a registry control plane project that is not public yet, but is intended to be released once it has seen enough real use and the rough edges are worked out.
I built it because I wanted a simple registry-based platform with garbage
collection and a maintenance mode. The foundation is a straightforward
registry:2 based path instead of something heavier.
Most of the work has been around making that simple base practical to operate: clear authentication flow, predictable image lifecycle handling, and enough control points to keep the day-to-day maintenance workload low.
That is where the project stands right now: active, private, and moving toward a public release once the implementation feels stable.