-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Push flux events when using a flux source #573
Comments
Hi @nicu-da, could you share a little more detail about what you'd like to see here? The controller should already be emitting these events for the stack-controller. Are you seeing those? Is the issue that you'd like the Flux notification-controller to more seamlessly pick these up? Or something else? |
Hi @blampe Thank you for the update. Indeed those events seem to be produced for the Stack but they are pure k8s events from what I can tell, and are missing the flux specific fields:
The reasoning to have those fields present is that I expect that should allow for fluxcd alerts to be generated in this case, thus triggering slack notifications for stack events. The only way I can think of to get notified about stack events currently is using something like https://github.com/kubeshop/botkube, but that adds one more layer, but please correct me if I'm wrong and there's an easier way to get real time notifications around the stack events. |
Added to epic #586 |
Hello!
Issue details
Unless I'm missing something, there is no easy way to get notifications for when a stack CR is being updated, it has failed, it started reconciling actual differences, it has finished reconciling and so on.
I would've expected this is included in the flux source integration, and that events are published from the stack controller.
Affected area/feature
Flux integration
The text was updated successfully, but these errors were encountered: