Skip to content

OSDOCS-16837: Standard Network Policy CQA2#111308

Open
jab-rh wants to merge 1 commit into
openshift:mainfrom
jab-rh:OSDOCS-16837
Open

OSDOCS-16837: Standard Network Policy CQA2#111308
jab-rh wants to merge 1 commit into
openshift:mainfrom
jab-rh:OSDOCS-16837

Conversation

@jab-rh
Copy link
Copy Markdown
Contributor

@jab-rh jab-rh commented May 6, 2026

@jab-rh jab-rh added this to the Continuous Release milestone May 6, 2026
@jab-rh jab-rh self-assigned this May 6, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 6, 2026
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented May 6, 2026

@jab-rh: This pull request references OSDOCS-16837 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

Version(s):

Issue:

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label May 6, 2026
@ocpdocs-previewbot
Copy link
Copy Markdown

🤖 Wed May 06 16:40:08 - Prow CI generated the docs preview:
https://111308--ocpdocs-pr.netlify.app
Complete list of updated preview URLs: artifacts/updated_preview_urls.txt

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented May 6, 2026

@jab-rh: 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.

@jab-rh jab-rh added the merge-review-needed Signifies that the merge review team needs to review this PR label May 8, 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 11, 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.

A few things to consider. Thanks, Jason.

<1> Replace `<project>` with the name for the project you are creating.
+
--
where:
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.

----
<1> Replace `<project>` with the name for the project you are creating.
+
--
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
--
Replace <project>` with the name of the project you want to create.

podSelector: {}
policyTypes:
- Ingress
----
<1> `policy-group.network.openshift.io/ingress:""` label supports OVN-Kubernetes.

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.

The policy-group.network.openshift.io/ingress:"" label supports OVN-Kubernetes.

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.

@@ -6,6 +6,9 @@
[id="nw-networkpolicy-multitenant-isolation_{context}"]
= Configuring multitenant isolation by using network policy

[role="_abstract"]
You can configure network policies to isolate workloads in a project from pods and services in other namespaces. This isolation helps control network traffic between projects and improves multitenant security in your cluster.

You can configure your project to isolate it from pods and services in other
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.

You can probably get rid of this sentence since it repeats the first.

@@ -8,6 +8,9 @@
[id="nw-networkpolicy-project-defaults_{context}"]
= Adding network policies to the new project template

[role="_abstract"]
You can add `NetworkPolicy` objects to the default project template so that new projects automatically include predefined network isolation rules. Applying network policies through templates helps enforce consistent network security controls across projects.

As a cluster administrator, you can add network policies to the default template for new projects.
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.

Same here. If your abstracts rewrite some of these I'd just delete the old sentences.

@@ -8,6 +8,9 @@
[id="nw-networkpolicy-create-ocm_{context}"]
= Creating a network policy using {cluster-manager}

[role="_abstract"]
To control ingress and egress traffic for workloads in your cluster, create a network policy by using {cluster-manager}. Network policies help enforce namespace-level network isolation and improve application security.

To define granular rules describing the ingress or egress network traffic allowed for namespaces in your cluster, you can create a network policy.
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 would just use this as the abstract or because your re-write introduces new content you'll need to get QE.

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 jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. merge-review-in-progress Signifies that the merge review team is reviewing this PR size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants