You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feature request: propagate the events from pod running remotely to the proxy pod, so that user can monitor all pods without logging in to remote clusters. Also to see if the remote pod is having some kind of error in the local proxy pod.
The text was updated successfully, but these errors were encountered:
adrienjt
changed the title
Propagate pod status updates to the proxy pod
Propagate events involving delegate pods from target to source cluster
May 15, 2020
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.
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.
Feature request: propagate the events from pod running remotely to the proxy pod, so that user can monitor all pods without logging in to remote clusters. Also to see if the remote pod is having some kind of error in the local proxy pod.
The text was updated successfully, but these errors were encountered: