Skip to content

[doc][KubeRay] Add NetworkPolicy user guide + kuberay namespace note - #65074

Open
chipspeak wants to merge 1 commit into
ray-project:masterfrom
chipspeak:add-kuberay-networkpolicy-docs
Open

[doc][KubeRay] Add NetworkPolicy user guide + kuberay namespace note#65074
chipspeak wants to merge 1 commit into
ray-project:masterfrom
chipspeak:add-kuberay-networkpolicy-docs

Conversation

@chipspeak

@chipspeak chipspeak commented Jul 28, 2026

Copy link
Copy Markdown

Description

Adding documentation around the new NetworkPolicy feature in KubeRay.

Related issues

ray-project/kuberay#5030

Additional information

N/A

@chipspeak
chipspeak force-pushed the add-kuberay-networkpolicy-docs branch from b65acbc to 38dbe13 Compare July 28, 2026 16:19
@machichima machichima self-assigned this Jul 29, 2026
@chipspeak
chipspeak marked this pull request as ready for review July 29, 2026 08:58
@chipspeak
chipspeak requested review from a team and andrewsykim as code owners July 29, 2026 08:58

@gemini-code-assist gemini-code-assist Bot left a comment

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.

Code Review

This pull request updates the KubeRay operator installation guide to use a dedicated ray-system namespace by default and introduces a comprehensive user guide for configuring RayCluster with NetworkPolicies. The review feedback identifies a critical issue in the Kustomize configuration example where a strategic merge patch would overwrite the operator's default arguments and break its functionality, recommending a JSON 6902 patch instead. Additionally, it suggests simplifying the validation instructions since the ray-system namespace is now the default for all installation methods.

## Step 3: Validate Installation

Confirm that the operator is running in the namespace `default`.
Confirm that the operator is running. If you installed into `ray-system`, pass `-n ray-system`:

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.

medium

Since both Method 1 (Helm) and Method 2 (Kustomize) in the updated guide now install the operator into the ray-system namespace by default, the conditional phrasing "If you installed into ray-system" is no longer necessary.

We can simplify this to:

Confirm that the operator is running in the `ray-system` namespace:

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

@machichima I'm happy to still have this in just to double down on the ray-system namespace advice but I can change it to the above too depending on what you think.

Comment thread doc/source/cluster/kubernetes/user-guides/network-policy.md
Signed-off-by: Pat O'Connor <paoconno@redhat.com>

Co-authored-by: David Adamache <dadamach@redhat.com>
Co-authored-by: Paul Nolan <pnolan@redhat.com>
@chipspeak
chipspeak force-pushed the add-kuberay-networkpolicy-docs branch from 38dbe13 to 826d9a4 Compare July 29, 2026 09:41
@ray-gardener ray-gardener Bot added docs An issue or change related to documentation core Issues that should be addressed in Ray Core community-contribution Contributed by the community labels Jul 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contributed by the community core Issues that should be addressed in Ray Core docs An issue or change related to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants