Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propagate events involving delegate pods from target to source cluster #28

Open
dimm0 opened this issue May 15, 2020 · 3 comments
Open
Labels
enhancement New feature or request

Comments

@dimm0
Copy link
Collaborator

dimm0 commented May 15, 2020

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.

@adrienjt 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
@adrienjt
Copy link
Contributor

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.

@adrienjt adrienjt added the enhancement New feature or request label May 15, 2020
@adrienjt
Copy link
Contributor

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.

@dimm0
Copy link
Collaborator Author

dimm0 commented May 15, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants