You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently kyverno mutation logs does not specify the path for the mutation or the actual action, the information about it’s buried under way too much information (which is expected from verbose level 6). Attached is the file for messages received on verbose level 6 with their mutation policies involved and one yaml spec deployed. we have to wade through a lot of information to get to this. (Search for “"path":"/spec/containers/" in the attached file)
Can this be enabled with a lower verbose level or as a flag option? while that is decided in kyverno/kyverno we should document this information being available at v6 admission-controller-logs-v6-path_spec.txt
Slack discussion
No response
The text was updated successfully, but these errors were encountered:
anushkamittal2001
changed the title
[Enhancement] Add information for where information about the logs are visible
[Enhancement] Add information about where path of mutation and actual action is available
Aug 26, 2024
Description
Currently kyverno mutation logs does not specify the path for the mutation or the actual action, the information about it’s buried under way too much information (which is expected from verbose level 6). Attached is the file for messages received on verbose level 6 with their mutation policies involved and one yaml spec deployed. we have to wade through a lot of information to get to this. (Search for “"path":"/spec/containers/" in the attached file)
Can this be enabled with a lower verbose level or as a flag option? while that is decided in kyverno/kyverno we should document this information being available at v6
admission-controller-logs-v6-path_spec.txt
Slack discussion
No response
The text was updated successfully, but these errors were encountered: