dispatch handling and the Events API

[coryodaniel]

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:

• :ok, {:ok, _} -> Normal
• :error, {:error, _} -> Warning

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.

[coryodaniel]

~Could be done independently of #22. May be nice to wait and use that interface.~ #22 is merged.

Create a module around events

References:

• core/v1 events
• write operations

Regarding event occurrences count, consider a GenServer/Agent vs querying the k8s API and incrementing the count.

[coryodaniel]

Related: #5 #4 #2

[sleipnir]

Hi @mruoss Is it now possible to emit events to kubernetes API? Would they be available via kubectl get events or kubectl describe commands ?

[mruoss]

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...

[mruoss]

You can check guides/controllers.livemd (path to module is still hardcoded and needs to be changed, though)