Create Component for Viewing All Policies Based on Annotations on User's Group

[Jonas-Beck]

We should consider creating a component to get a global view of the policies, similar to the policy-reporter-ui. However, it should be based on annotations on the current user's group so that they only see policies for services that they own.

Tasks

• Add Initial Implementation of PolicyReportsPage
• Add support for selecting Namespace
• Add support for selecting Source
• Add support for selecting Kinds
• Add charts for easier global overview
• Update documentation
• Add Status filter instead of 3 tables
• Add Severity filter

[Jonas-Beck]

I’ve started working on a draft PR to add a PolicyReporterPage component for viewing policies across services. As a starting point, I’m implementing the same UI as the entity-based components. This component is intended to be added to the Backstage sidebar.

@andrewthauer, would this work as a starting point for you? It’s still a rough draft.

I’m also considering extending it with charts similar to the Policy Reporter UI, but that would likely come in a follow-up PR.

Screenshot

[andrewthauer]

@Jonas-Beck - Yes! This is more or less what I was able to create by making the annotations optional. We could definitely use this as our initial MVP vs the optional annotation workaround I cooked up.

[Jonas-Beck]

@andrewthauer, I have created a PR that adds an initial implementation of the PolicyReportsPage. However, I still need to test it with my own Backstage instance. I’ve also created some tasks in this issue for improvements that should be made in future PRs.

It would be great if you could help test this new component. If there’s anything you’d like to see that’s not already defined in the tasks, let me know, and I’ll make sure to add it.

If there’s a feature you need for your use case and you’d like to contribute, that would be awesome! Just let me know, and I can assign it to you.

[andrewthauer]

@Jonas-Beck - Sure, I can pull the branch down and test it in the next day or so. Quick glance, this seems to fit our initial MVP goal of being able see all fails across a cluster.

One small thing I did change in our current fork was allowing for a larger page size. I bumped page sized in increments up to 250. The performance was still very fast. I think this would be ideal to have until proper backend searching or sorting is supported. The default can obviously be lower.

[Jonas-Beck]

I think we could add a prop to the component to modify the page size options. But would this still be needed with a working search?

The PolicyReportPage doesn't have the same limitation as the entity-based components and makes use of the policy reporter API search filter when searching in the table, so it's not client-side searching anymore.

[andrewthauer]

I think we could add a prop to the component to modify the page size options. But would this still be needed with a working search?

The PolicyReportPage doesn't have the same limitation as the entity-based components and makes use of the policy reporter API search filter when searching in the table, so it's not client-side searching anymore.

Oh, that's really nice! I'll try and test this out today.

[andrewthauer]

After I updated the react dependencies in #62, I was able to test and verify the new PolicyReportPage. Works great. Thanks! I'll try and integrate this into our internal instance and then follow up with any additionally needed features, etc.