Skip to content

Syncing with Product PR #35 #186

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Syncing with Product PR #35 #186

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/05.policy/13.usingcrd/13.usingcrd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ The NvGroupDefinition custom resource represents a group's definition (`criteria

#### Schema Attribute: `name_referral`

NeuVector v5.4.3 adds the attribute `name_referral` (boolean) as a setting in the group selector(`target.selector`, `ingress.items[].selector`, `egress.items[].selector`) in the NvSecurityRule/NvClusterSecurityRule CRD schema.
Starting with v5.4.3, NeuVector utilizes the attribute `name_referral` (boolean) as a setting in the group selector(`target.selector`, `ingress.items[].selector`, `egress.items[].selector`) in the NvSecurityRule/NvClusterSecurityRule CRD schema. You can enable this setting in the UI by checking "Use Name Referral" in the Groups Export dialog.

If the `name_referral` attribute is set to `true`, the `criteria/comment` fields of the group selector in NvSecurityRule/NvClusterSecurityRule are ignored by NeuVector. This means that NeuVector will try to determine the group's `criteria/comment` by referral. This introduces "group referral" in NvSecurityRule/NvClusterSecurityRule CRDs to assist with modifications when editing groups. If unset then users will need to update groups in each defined place in the respective yaml files if modifications are needed.

Expand Down
2 changes: 1 addition & 1 deletion versioned_docs/version-5.4/05.policy/13.usingcrd/13.usingcrd.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ The NvGroupDefinition custom resource represents a group's definition (`criteria

#### Schema Attribute: `name_referral`

NeuVector v5.4.3 adds the attribute `name_referral` (boolean) as a setting in the group selector(`target.selector`, `ingress.items[].selector`, `egress.items[].selector`) in the NvSecurityRule/NvClusterSecurityRule CRD schema.
Starting with v5.4.3, NeuVector utilizes the attribute `name_referral` (boolean) as a setting in the group selector(`target.selector`, `ingress.items[].selector`, `egress.items[].selector`) in the NvSecurityRule/NvClusterSecurityRule CRD schema. You can enable this setting in the UI by checking "Use Name Referral" in the Groups Export dialog.

If the `name_referral` attribute is set to `true`, the `criteria/comment` fields of the group selector in NvSecurityRule/NvClusterSecurityRule are ignored by NeuVector. This means that NeuVector will try to determine the group's `criteria/comment` by referral. This introduces "group referral" in NvSecurityRule/NvClusterSecurityRule CRDs to assist with modifications when editing groups. If unset then users will need to update groups in each defined place in the respective yaml files if modifications are needed.

Expand Down