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

event-namespace doesn't appear to work #977

Open
tzneal opened this issue Oct 16, 2024 · 4 comments
Open

event-namespace doesn't appear to work #977

tzneal opened this issue Oct 16, 2024 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@tzneal
Copy link

tzneal commented Oct 16, 2024

When using a non-default event-namespace, events don't appear to get emitted.

From the code, there are two cases:

  • If there is no involved object, event must be in the default namespace
  • The event must be in the namespace of the object (default or empty namespace for Node objects)

Does this option serve another purpose?

@dims
Copy link
Member

dims commented Oct 17, 2024

@tzneal is this related? kubernetes/kubernetes#89062 (comment)

@tzneal
Copy link
Author

tzneal commented Oct 17, 2024

Maybe so, there doesn't seem to be clear docs about it and if this should work.

@liggitt
Copy link
Member

liggitt commented Oct 18, 2024

I don't think kubernetes/kubernetes#89062 (comment) is related to the namespace issue

The rule for events is that they have to be in the same namespace as the related object, or the default namespace for cluster-scoped objects

@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants