-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Include security options in the container created event #31557
Conversation
LGTM |
GCE e2e build/test passed for commit 785c83c. |
@k8s-bot test this [submit-queue is verifying that this PR is safe to merge] |
GCE e2e build/test passed for commit 785c83c. |
Automatic merge from submit-queue |
I'm kind of confused why I, as a user, would care about this? It shows up in events for every user in the system - is it supposed to be actionable? What is it telling me that I need to know? The referenced issue doesn't actually clearly articulate why this message is important enough that everyone needs to see it. |
As a clarification - events are primarily to help users. I know this helps some users... it just doesn't help many of them. Maybe 2. Or 3. Can we move this somewhere more relevant, like very deeply buried in status where only someone who cares can see it? |
Or as an event annotation? |
I like that suggestion. Eventually this should be moved out to the monitoring pipeline anyway. |
New container creation events look like:
The goal is to provide enough information to confirm that the requseted security constraints were honored.
For #31284
/cc @dchen1107 @thockin @jfrazelle @pweil- @pmorie
Justification for v1.4:
This change is