We currently send Flux events to Weave Cloud as events allowing upstreams to be aware of syncs, releases, and other events in Flux.
It would be great to be able to produce events from the helm-operator whenever it makes changes (or fails to make changes).
Are there any plans for sending events from the helm-operator upstream?
Yes, though not well-formed plans.
Briefly: the simplest thing would be to give the helm-operator an upstream URL, the same as for fluxd, and let it post its events there.
The helm operator already generates _Kubernetes_ events though, and this would be doubling up .. So another more decoupled design is to use the Kubernetes event mechanism for fluxd too, and have a listener that posts both sets of events to the upstream.
The easy (first) option above would be fine as a start. I should note here that the helm operator currently generates Kubernetes events, but erroneously (it sends a success event whatever happens). An implementation either of the alternatives above would have to be more careful :-)
Any updates on this?
It would be nice to have it!
Duplicate of #11
Most helpful comment
Any updates on this?
It would be nice to have it!