I just had fun writing about #Harbor, a technology everybody 'knows' is the obvious choice as container registry to explore when and why that's true, because it led to all kinds of interesting questions about the role of cloud registries and portability as well as how mature projects progress
as usual with open source, the community is a huge part of the success of Harbor (and my thanks to everyone in the community who talked to me about it); it was also salutory to see how open source & the CNCF make it almost irrelevant what Broadcom does (except to the people working there of course)
It's always 'interesting' when open source and changing business directions collide: I always try to talk to project founders as well as current maintainers but it's been difficult to get to the folks at Broadcom recently...
A number of the maintainers work on Tanzu which uses Harbor as its registry; since Broadcom bought VMware, the situation of Tanzu and how Broadcom will be involved in Harbor going forward is a little unclear (they didn’t make it to Kubecon I believe) though the Harbor *project* is still going strong
The obvious choice of Kubernetes registry keeps getting new features: its continuing relevance is one of the success stories of the CNCF
open source
platform engineering
Kubernetes
Harbor
CNCF
OCI
Docker
Helm
software supply chain
SBOMs
Cyber Resiliency Act
artefacts