Propagate events involving delegate pods from target to source cluster about admiralty HOT 3 OPEN

Status (part of the pod object) is already fed back. What you want is events (different objects referring to the pod), which are gathered and shown alongside pod info with kubectl describe.

from admiralty.

Here are a couple of initial thoughts:

• We'd want to make sure the source cluster doesn't see events that are not related to its delegate pods, for security reasons. With a combination of RBAC and OPA? Some indirection using controller logic?
• When we create event copies in the source cluster, we should modify the involvedObject field to refer to the proxy pod, so they can be displayed with kubectl describe.

from admiralty.

I guess since the controller will propagate those, it can have some logic to filter the events

from admiralty.