Package record has all client logic for recording and reporting events.
Event constructs an event from the given information and puts it in the queue for sending. 'object' is the object this event is about. Event will make a reference-- or you may also pass a reference to the object directly. 'status' is the new status of the object. 'reason' is the reason it now has this status. Both 'status' and 'reason' should be short and unique; they will be used to automate handling of events, so imagine people writing switch statements to handle them. You want to make that easy. 'message' is intended to be human readable.
The resulting event will be created in the same namespace as the reference object.
Eventf is just like Event, but with Sprintf for the message field.
GetEvents lets you see *local* events. Convenience function for testing. The return value can be ignored or used to stop logging, if desired.
StartLogging just logs local events, using the given logging function. The return value can be ignored or used to stop logging, if desired.
StartRecording starts sending events to recorder. Call once while initializing your binary. Subsequent calls will be ignored. The return value can be ignored or used to stop recording, if desired.
EventRecorder knows how to store events (client.Client implements it.) EventRecorder must respect the namespace that will be embedded in 'event'. It is assumed that EventRecorder will return the same sorts of errors as pkg/client's REST client.