Post events for cluster-scoped objects to current namespace

[nolar]

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)

[zincr]

🤖 zincr found 0 problems , 0 warnings

✅ Large Commits
✅ Approvals
✅ Specification
✅ Dependency Licensing

[zincr]

🤖 zincr found 1 problem , 0 warnings

❌ Approvals
✅ Large Commits
✅ Specification
✅ Dependency Licensing

Details on how to resolve are provided below

---

Approvals

All proposed changes must be reviewed by project maintainers before they can be merged

Not enough people have approved this pull request - please ensure that 1 additional user, who have not contributed to this pull request approve the changes.

• ✅ Approved by PR author @nolar
• ❌ 1 additional approval needed
   

[s-soroosh]

is this safe to keep refs with id None if the owner's uid is None?
not sure if both owner's uid and ref's uid can be None is the same time though!

[nolar]

Perhaps, ref['uid'] is mandatory. I was replacing these things in almost automated way, didn't pay attention (previously, it would fail with a KeyError in such cases).

The only case, when this can happen so that ref['uid'] is None/absent, is when we create both the owner & the child, and keep them in-memory, not yet posted to the API, therefore not yet having the uids — and then we try to connect them. Adding an additional 2nd owner would hit this mach None == None, despite the 1st & 2nd owners can have different apiVersion/kind/name.

This is quite an artificial case. I'm not even sure if it is possible to add owner references without a uid, just by a name. We can solve it in advance, but maybe as a separate PR — not related to the event-posting. And I'm not even sure how to properly reproduce this scenario.