Value Statement

When a user configures the discovery settings in their cluster, they will be able to filter discovered cluster resources based on the infrastructure provider of the cluster. This ensures that users can efficiently manage and view only relevant clusters based on their infrastructure, improving usability and operational efficiency.

Supported cluster types include:

• aws
• azure
• baremetal
• external
• gcp
• ibmcloud
• kubevirt
• libvirt
• none
• nutanix
• openstack
• ovirt
• powervs
• vsphere

Definition of Done for Engineering Story Owner (Checklist)

• [ ] Users can filter discovered clusters by infrastructure provider in the Discovery UI.

• [ ] Users can apply multiple infrastructure provider filters in the Discovery UI.

• [ ] DiscoveryConfig reflects the selected infrastructure provider filters.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the Customer

Portal Doc template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

• [ ] The must-gather script has been updated.