One option to tackle this issue is for the PolicyReport API to provide some kind of contract between PolicyReport generators and consumers.
The proposal here is to add a Configuration field to the API -
This defines the max number of reports that will be stored. Also, provide a way to store only reports that the user may be interested in - the statusFilter allows to filter based on different status values - pass, fail, error, warn, skip.
The setting of these values should be exposed via the PolicyReport generator (for example, policy engines). The PolicyReport API should provide sane defaults for these fields
Some scale issues identified for
PolicyReport
can be found in this thread - https://github.com/open-policy-agent/gatekeeper/issues/2394One option to tackle this issue is for the
PolicyReport
API to provide some kind of contract betweenPolicyReport
generators and consumers. The proposal here is to add aConfiguration
field to the API -This defines the max number of reports that will be stored. Also, provide a way to store only reports that the user may be interested in - the statusFilter allows to filter based on different status values -
pass, fail, error, warn, skip.
The setting of these values should be exposed via thePolicyReport
generator (for example, policy engines). ThePolicyReport
API should provide sane defaults for these fields