- [VOTE] Harbor moving to incubation
Re: [VOTE] Harbor moving to incubation
toggle quoted messageShow quoted text
I genuinely appreciate Justin's feedback on these votes. If I'm not intimately familiar with the project/product I often wait for Justin's input prior to voting. I wholeheartedly encourage Justin's input on these votes. They bring up bigger points and provide levity to the process. Any effort to not have this feedback on the record should be discouraged, in my opinion.
I'm well aware of the adoption and uses of Harbor. My company runs it and my criticisms come from first hand experience as a user and operator of the software.
I'm happy to move my feedback out of this thread so voting can continue without any extra noise.
On Tue, Nov 6, 2018 at 4:27 PM Haining Zhang <hi@...
(in reponse to Justin's comment)
Though Harbor may not be the only solution to a private registry,
thousands of users choose Harbor to manage container images in
their production environments. The user base includes many large
internet companies and enterprises in the world. In some
environments, Harbor manages tens of thousands of images and
supports thousands of container hosts. Typical use cases of Harbor
include RBAC on images, image replication across geographically
distributed locations, vulnerability scanning etc.
On 11/7/18 3:21 AM, Justin Garrison
understand the need for container registries in a
containerized environment, but I'm not sold Harbor being the
solution for most people's needs when they need to run their
Please vote (+1/0/-1) by replying to this
thread; the full proposal located here: https://github.com/cncf/toc/pull/163
Remember that the TOC has binding votes only,
but we do appreciate non-binding votes from
the community as a sign of support!
Chris Aniszczyk (@cra) |
Join email@example.com to automatically receive all group messages.