community
community copied to clipboard
goharbor
Harbor and CDEvents
Harbor recently introduced support for CloudEvents (kudos!), which makes it possible for consumers to watch those events, react to them and/or store them for records.
The CDEvents project, incubated at the CD Foundation, aims to standardise the content of events in the continuous delivery space, thus introducing interoperability across different tools.
CDEvents is being implemented by a number of tools like Jenkins, Spinnaker, Tekton, Testkube, Argo, and more.
One interesting feature of Argo CD is its ability to react to a new tag being published for an artifact, and automatically trigger a new deployment as well as a new PR to keep the git repo up to date as well. Argo CD today has to rely on polling only - a standard event sent by a registry on PUSH would allow Argo CD to react instantaneously.
Having all tools generating CDEvents allows organisations to collect all those events, and use them to build audit trails, and visualisations and trigger the next step in event-driven workflows.
I would like to author, with some help from the Harbor community, a proposal to integrate CDEvents in Harbor. I started a draft proposal in an hackmd document, feedback and input are welcome. Once the draft proposal looks ok, I can submit a PR - but please let me know if I should follow I different workflow.
@afrittoli how is it going with this are we close to closing and implementing it?
@chlins and @wy65701436
@afrittoli how is it going with this are we close to closing and implementing it?
@OrlinVasilev I posted a proposed way forward in https://github.com/goharbor/community/pull/229#discussion_r1265090884 but got no reply. Do you have a suggestion on a possible way forward? Would it help to bring the discussion to the working group meeting?