You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Starting from the assets will bring a better experience. Curretly the user can only start from the policy, in the policy, they can set which namespace or workload they want to scan. However, there is no place on the UI to let the user see what assets do they have.
Describe the solution you'd like
I would like to add a crd called asset, it will contain all the asset metadata, has the datasource for UI.
I would like to add another crd called asset2policy map, which will contain the mapping relationship from the assets to the policies
Describe alternatives you've considered
Describe the main design/architecture of your solution
Describe the development plan you've considered
Additional context
The text was updated successfully, but these errors were encountered:
JingChen23
changed the title
Feature: Make the user able to review the assets, and bind policy for each asset
Epic: Make the user able to review the assets, and bind policy for each asset
Dec 14, 2022
Is your feature request related to a problem? Please describe.
Starting from the assets will bring a better experience. Curretly the user can only start from the policy, in the policy, they can set which namespace or workload they want to scan. However, there is no place on the UI to let the user see what assets do they have.
Describe the solution you'd like
I would like to add a crd called asset, it will contain all the asset metadata, has the datasource for UI.
I would like to add another crd called asset2policy map, which will contain the mapping relationship from the assets to the policies
Describe alternatives you've considered
Describe the main design/architecture of your solution
Describe the development plan you've considered
Additional context
The text was updated successfully, but these errors were encountered: