-
-
Notifications
You must be signed in to change notification settings - Fork 27
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
dispatch handling and the Events API #5
Comments
Hi @mruoss Is it now possible to emit events to kubernetes API? Would they be available via kubectl get events or kubectl describe commands ? |
With the next version, yes. But although we have integration tests now, this requires some "production approval". Next version is probably going to be an RC... |
You can check guides/controllers.livemd (path to module is still hardcoded and needs to be changed, though) |
While it is up the the individual controller to handle error cases, it would be nice to integrate the result of a controller dispatch with the kubernetes events API.
Return from add/modify/delete/reconcile would automatically create events:
There are a lot of fields for an Event. It would be nice to abstract as much of this away as possible, but allow for an explicit return value of something like
{:ok, %K8s.Event{}}
(doesnt exist) to override any logic bonny provides.The text was updated successfully, but these errors were encountered: