Thanks to visit codestin.com
Credit goes to github.com

Skip to content

OCPBUGS-59523 - Update installation-usage.md to clarify audit log location#3024

Merged
saschagrunert merged 1 commit into
kubernetes-sigs:mainfrom
BhargaviGudi:bgudi_OCPBUGS-59523
Oct 14, 2025
Merged

OCPBUGS-59523 - Update installation-usage.md to clarify audit log location#3024
saschagrunert merged 1 commit into
kubernetes-sigs:mainfrom
BhargaviGudi:bgudi_OCPBUGS-59523

Conversation

@BhargaviGudi
Copy link
Copy Markdown
Contributor

@BhargaviGudi BhargaviGudi commented Oct 14, 2025 •
edited by saschagrunert
Loading

What type of PR is this?
/kind bug
/documentation

What this PR does / why we need it:
This PR updates the installation-usage.md documentation to clarify where the audit log file generated by the JsonEnricher is stored. Currently, the documentation does not make it clear that the log file is written to the node's file system (not inside the pod), which can lead to confusion for users monitoring audit logs.

Which issue(s) this PR fixes:
Fixes documentation inconsistency observed when enabling JsonEnricher in the Security Profiles Operator.
Fixes bug: https://issues.redhat.com/browse/OCPBUGS-59523

Does this PR have test?
N/A — documentation-only change.

Special notes for your reviewer:
Does this PR introduce a user-facing change?

Update installation-usage.md to clarify audit log location

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 14, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Oct 14, 2025

Hi @BhargaviGudi. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Oct 14, 2025
@BhargaviGudi BhargaviGudi mentioned this pull request Oct 14, 2025
Closed
@k8s-ci-robot k8s-ci-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Oct 14, 2025
@saschagrunert
Copy link
Copy Markdown
Member

saschagrunert commented Oct 14, 2025

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Oct 14, 2025
saschagrunert
saschagrunert approved these changes Oct 14, 2025
View reviewed changes
Copy link
Copy Markdown
Member

@saschagrunert saschagrunert left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! The e2e tests are broken right now but I assume we can merge manually if the rest of the CI passes.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 14, 2025
@k8s-ci-robot
Copy link
Copy Markdown
Contributor

k8s-ci-robot commented Oct 14, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BhargaviGudi, saschagrunert

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 14, 2025
@codecov-commenter
Copy link
Copy Markdown

codecov-commenter commented Oct 14, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 26.56%. Comparing base (11d77f4) to head (e6d8dd0).
⚠️ Report is 1006 commits behind head on main.

Additional details and impacted files 
@@             Coverage Diff             @@
##             main    #3024       +/-   ##
===========================================
- Coverage   45.50%   26.56%   -18.95%     
===========================================
  Files          79      125       +46     
  Lines        7782    20921    +13139     
===========================================
+ Hits         3541     5557     +2016     
- Misses       4099    15080    +10981     
- Partials      142      284      +142
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@saschagrunert saschagrunert merged commit 7b7a517 into kubernetes-sigs:main Oct 14, 2025
29 of 33 checks passed
@saschagrunert saschagrunert mentioned this pull request Apr 1, 2026
Closed
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@saschagrunert saschagrunert saschagrunert approved these changes

@ngopalak-redhat ngopalak-redhat Awaiting requested review from ngopalak-redhat

@Vincent056 Vincent056 Awaiting requested review from Vincent056

Assignees

@saschagrunert saschagrunert

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@BhargaviGudi @k8s-ci-robot @saschagrunert @codecov-commenter