Skip to content

[OSDOCS-16840] PR 1 of 4 for ANP ADV audits#112297

Open
stevsmit wants to merge 1 commit into
openshift:mainfrom
stevsmit:16840-osdocs
Open

[OSDOCS-16840] PR 1 of 4 for ANP ADV audits#112297
stevsmit wants to merge 1 commit into
openshift:mainfrom
stevsmit:16840-osdocs

Conversation

@openshift-ci openshift-ci Bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 26, 2026
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 26, 2026

@stevsmit: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

@stevsmit stevsmit added this to the Continuous Release milestone May 27, 2026
@stevsmit stevsmit added the merge-review-needed Signifies that the merge review team needs to review this PR label May 27, 2026
@stevsmit stevsmit changed the title PR 1 of 4 for ANP ADV audits [OSDOCS-16840] PR 1 of 4 for ANP ADV audits May 27, 2026
@JoeAldinger JoeAldinger added merge-review-in-progress Signifies that the merge review team is reviewing this PR and removed merge-review-needed Signifies that the merge review team needs to review this PR labels May 27, 2026
Copy link
Copy Markdown
Contributor

@JoeAldinger JoeAldinger left a comment

Choose a reason for hiding this comment

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

/lgtm small suggestion


Audit logging is enabled per `AdminNetworkPolicy` CR by annotating an ANP policy with the `k8s.ovn.org/acl-logging` key such as in the following example:
[role="_abstract"]
You can enable audit logging for individual `AdminNetworkPolicy` custom resources in {product-title} by annotating each policy with the `k8s.ovn.org/acl-logging` key. Use the resulting logs to verify how `allow`, `deny`, and `pass` rules affect traffic between namespaces.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
You can enable audit logging for individual `AdminNetworkPolicy` custom resources in {product-title} by annotating each policy with the `k8s.ovn.org/acl-logging` key. Use the resulting logs to verify how `allow`, `deny`, and `pass` rules affect traffic between namespaces.
You can enable audit logging for individual `AdminNetworkPolicy` custom resources in {product-title} by annotating each policy with the `k8s.ovn.org/acl-logging` key. Use the resulting logs to verify how `Allow`, `Deny`, and `Pass` rules affect traffic between namespaces.

You can enable audit logging for individual `AdminNetworkPolicy` custom resources in {product-title} by annotating each policy with the `k8s.ovn.org/acl-logging` key. Use the resulting logs to verify how `allow`, `deny`, and `pass` rules affect traffic between namespaces.

.Example of annotation for `AdminNetworkPolicy` CR
[%collapsible]
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I'd take these out if it were me.


As a cluster administrator, you can enable audit logging for a namespace.
[role="_abstract"]
To enable egress firewall and network policy audit logging for a namespace in {product-title}, you can add the `k8s.ovn.org/acl-logging` annotation with the `oc annotate` command. You can also apply a namespace YAML file that sets `allow` and `deny` log severity levels.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
To enable egress firewall and network policy audit logging for a namespace in {product-title}, you can add the `k8s.ovn.org/acl-logging` annotation with the `oc annotate` command. You can also apply a namespace YAML file that sets `allow` and `deny` log severity levels.
To enable egress firewall and network policy audit logging for a namespace in {product-title}, you can add the `k8s.ovn.org/acl-logging` annotation with the `oc annotate` command. You can also apply a namespace YAML file that sets `Allow` and `Deny` log severity levels.

toc::[]

[role="_abstract"]
The OVN-Kubernetes network plugin uses Open Virtual Network (OVN) access control lists (ACLs) to manage `AdminNetworkPolicy`, `BaselineAdminNetworkPolicy`, `NetworkPolicy`, and `EgressFirewall` objects. Audit logging exposes `allow` and `deny` ACL events for `NetworkPolicy`, `EgressFirewall` and `BaselineAdminNetworkPolicy` custom resources (CR). Logging also exposes `allow`, `deny`, and `pass` ACL events for `AdminNetworkPolicy` (ANP) CR.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Suggested change
The OVN-Kubernetes network plugin uses Open Virtual Network (OVN) access control lists (ACLs) to manage `AdminNetworkPolicy`, `BaselineAdminNetworkPolicy`, `NetworkPolicy`, and `EgressFirewall` objects. Audit logging exposes `allow` and `deny` ACL events for `NetworkPolicy`, `EgressFirewall` and `BaselineAdminNetworkPolicy` custom resources (CR). Logging also exposes `allow`, `deny`, and `pass` ACL events for `AdminNetworkPolicy` (ANP) CR.
The OVN-Kubernetes network plugin uses Open Virtual Network (OVN) access control lists (ACLs) to manage `AdminNetworkPolicy`, `BaselineAdminNetworkPolicy`, `NetworkPolicy`, and `EgressFirewall` objects. Audit logging exposes `Allow` and `Deny` ACL events for `NetworkPolicy`, `EgressFirewall` and `BaselineAdminNetworkPolicy` custom resources (CR). Logging also exposes `Allow`, `Deny`, and `Pass` ACL events for `AdminNetworkPolicy` (ANP) CR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

branch/enterprise-4.20 branch/enterprise-4.21 branch/enterprise-4.22 merge-review-in-progress Signifies that the merge review team is reviewing this PR ok-to-merge size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants