Epic Goal

Users are able to customize which resources are allowed/denied by the search-collector. The UI should allow for easier customization of the "search-collector-config" ConfigMap which stores the allowed/denied resources.

ex: 

{
  apiVersion: "v1",
  kind: "ConfigMap",
  metadata: {
    name: "search-collector-config",
    namespace: "<namespace where search-collector add-on is deployed>"
  },
  data: {
    AllowedResources: [
      {
        apiGroups: [
          "*"
        ],
        resources: [
          "services",
          "pods"
        ]
      },
    ],
    DeniedResources: [],
  }
} 

Why is this important?

...

Scenarios

...

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ...

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>