Namespace for events whose involvedObject is cluster-scoped

[xinlaini]

Hello,
We have a CRD that's cluster-scoped, in its controller, we are trying to create relevant events related to this CR. Since Event itself is namespace-scoped, we have to set the namespace for the event when posting the create request. We have tried 3 options:

1. setting event' namespace to our CRD controller's namespace (app-specific): this seems to be the most reasonable option, however, its rejected by the server due to "involved object's namespace does not match event.namespace":

2. setting event's namespace to "", this arguably makes sense since our CRD is cluster-scope, and one could argue posting its related events against "" namespace is reasonable. However, this was rejected by the client-go request preflight validation

3. setting event's namespace to "default", this works, however we feel uncomfortable because this doesn't seem to be as clean as 1 or 2.
   thoughts?
   Thanks!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[luebken]

Can we re-open this?

I'm happy to answer questions from a Crossplane perspective. My use-case is I would like to filter events of a Crossplane ManagedResource which happens to be cluster-scoped.

[k8s-ci-robot]

@m-messiah: You can't reopen an issue/PR unless you authored it or you are a collaborator.

In response to this:

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.