text: Title: [PR] Post events for cluster-scoped objects to current namespace
  Body: > <a href="https://github.com/nolar"><img align="left" height="50" src="https://avatars0.githubusercontent.com/u/544296?v=4"></a>        A pull request by [nolar](https://github.com/nolar) at _2019-08-05 18:06:51+00:00_
  > Original URL: https://github.com/zalando-incubator/kopf/pull/165
  > Merged by [nolar](https://github.com/nolar) at _2019-08-07 17:45:11+00:00_
  
  K8s-events cannot be posted cluster-scoped (?), and attached to cluster-scoped resources via API. However, we post them to the current namespace — so that they are not lost completely.
  
  > Issue : #164
  
  ## Description
  
  See #164 for details. 
  
  Brief summary: K8s events are namespaced, there are no cluster-scoped events. Also, k8s events can refer to an object via spec.involvedObject of type ObjectReference. This structure contains namespace field, to refer to the involved object's namespace (also, name, uid, etc).
  
  I could not find a way to post namespaced events for cluster-scoped resources. It always fails with namespace mismatch (regardless of which library is used). Event via `curl` — see the issue comments.
  
  So, we post the k8s-events to the current namespace, so that they are available via `kubectl get events`, despite they are not seen in `kubectl describe` on the involved objects. 
  
  It is not a full problem solution, but it is a bit better than just losing them completely.
  
  ## Types of Changes
  
  - Bug fix (non-breaking change which fixes an issue)
  