rancher
/
neuvector-product-docs
mirror of https://github.com/rancher/neuvector-product-docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update usingcrd.adoc 

Clarified "Use Name Referral"
This commit is contained in:
jorn 2025-05-14 13:20:48 -05:00 committed by GitHub
parent d42f3f055a
commit 207c503371
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/5.4/modules/en/pages/usingcrd.adoc
View File

@ -40,7 +40,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.