Admission Events InvolvedObject Namespace

[ctrought]

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

Enabled admission events and observed violations that generate events.

1. The events are generated in the gatekeeper namespace.
2. The InvolvedObject namespace is also incorrectly set as gatekeeper-system

https://open-policy-agent.github.io/gatekeeper/website/docs/customize-startup/#alpha-emit-admission-and-audit-events

What did you expect to happen:

1. I think it would be preferred if the event could be generate in the namespace where the violation occurred if it is a namespace scoped resource. This would allow the user to see some kind of trail of what happened, or what may still be occurring when the violations are occurring in the background. We also want to use third party tooling capable of exporting kubernetes events to alertmanager/slack for alerting Alerting integration for violations #580 that typically work based off the namespace where the event is located.
2. The InvolvedObjects namespace should likely also point to the actual namespace where the object exists regardless of which namespace the event is emitted in.

Environment:

• Gatekeeper version: 3.9.0
• Kubernetes version: (use kubectl version): 1.23

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[ctrought]

/active

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

[ctrought]

Active