rancher / rancher

Complete container management platform
http://rancher.com
Apache License 2.0
23.32k stars 2.96k forks source link

[RFE] NeuVector launch icon can be shown for user who has one of the permission from permission.neuvector.com/v1 #46552

Open selvamt94 opened 2 months ago

selvamt94 commented 2 months ago

Is your feature request related to a problem? Please describe. NeuVector release 5.4 will be supporting allowing Rancher Manager user with NeuVector granular permission such as user can only do realtime scan function. NeuVector launch icon is not known for those users to start SSO to NeuVector UI. User either need to add additional permission on the cattle-neuvector-system namespace to get the launch icon shown or need to construct below URL to launch NeuVector UI from browser new tab.

https://rancher-dev.nvqa.com/api/v1/namespaces/cattle-neuvector-system/services/https:neuvector-service-webui:8443/proxy/#/dashboard

Describe the solution you'd like Add cattle-neuvector-system namespace permission to users with one of the read or write permission from the below list

neuvector@ubuntu2204-rke-hardened-master-calico-auto:~/nv/feature/rancher-rbac$ kubectl api-resources |grep neuvector | grep permission
nvpermissiondefs                                          neuvector.com/v1                       true         NvPermissionDef
admissioncontrol                                          permission.neuvector.com/v1            false        AdmissionControl
auditevents                                               permission.neuvector.com/v1            false        AuditEvents
authentication                                            permission.neuvector.com/v1            false        Authentication
authorization                                             permission.neuvector.com/v1            false        Authorization
ciscan                                                    permission.neuvector.com/v1            false        CIScan
cluster                                                   permission.neuvector.com/v1            false        Cluster
compliance                                                permission.neuvector.com/v1            false        Compliance
events                                                    permission.neuvector.com/v1            false        Events
federation                                                permission.neuvector.com/v1            false        Federation
namespace                                                 permission.neuvector.com/v1            false        Namespace
registryscan                                              permission.neuvector.com/v1            false        RegistryScan
runtimepolicy                                             permission.neuvector.com/v1            false        RuntimePolicy
runtimescan                                               permission.neuvector.com/v1            false        RuntimeScan
securityevents                                            permission.neuvector.com/v1            false        SecurityEvents
systemconfig                                              permission.neuvector.com/v1            false        SystemConfig
vulnerability                                             permission.neuvector.com/v1            false        Vulnerability

Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered.

Additional context Standard user with below custom global regscan-write permission can not launch NeuVector UI because launch icon will not be available for this user. regscan-write-permission

The user need to have below permission on the project that include cattle-neuvector-system namespace to display NeuVector launch icon NeuVector-Launch-Permission

github-actions[bot] commented 5 days ago

This repository uses an automated workflow to automatically label issues which have not had any activity (commit/comment/label) for 60 days. This helps us manage the community issues better. If the issue is still relevant, please add a comment to the issue so the workflow can remove the label and we know it is still valid. If it is no longer relevant (or possibly fixed in the latest release), the workflow will automatically close the issue in 14 days. Thank you for your contributions.