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

[BhargaviGudi]

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?

NONE

[k8s-ci-robot]

Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

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.

[linux-foundation-easycla]

• ❌ The email address for the commit (783778f) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BhargaviGudi
Once this PR has been reviewed and has the lgtm label, please assign ccojocar for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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]

Welcome @BhargaviGudi!

It looks like this is your first PR to kubernetes-sigs/security-profiles-operator 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/security-profiles-operator has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

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.

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.

[saschagrunert]

@BhargaviGudi thank you for the PR! Please sign the CLA for this one.

[saschagrunert]

/check-cla

[BhargaviGudi]

I have signed CLA document as individual contributor and still observing failure in this PR as Missing CLA Authentication

[codecov-commenter]

Codecov Report

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

Additional details and impacted files

@@             Coverage Diff             @@
##             main    #2994       +/-   ##
===========================================
- 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]

• he email address for the commit (8890e3f) is not linked to the GitHub account, preventing the EasyCLA check.

Have you checked this comment?

The email address for the commit (8890e3f) is not linked to the GitHub account, preventing the EasyCLA check.

[ngopalak-redhat]

/check-cla

[saschagrunert]

/check-cla

[saschagrunert]

/check-cla

[BhargaviGudi]

/retest

[k8s-ci-robot]

@BhargaviGudi: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

[ngopalak-redhat]

/check-cla

[BhargaviGudi]

Closing this PR as I have created new PR to resolve EasyCLA authentication issue.