Value Statement

For server foundation, no additional specific test scenarios should be added. The scenarios you've collected now are sufficient for foundation. Just need to validate the following in each scenario:
1. the cpu/memory usage of the pods "ocm-proxyserver" in the "multicluster-engine" namespace on the hub
2. the latency of the kubevirtprojects.clusterview.open-cluster-management.io API

It is not mandatory to validate this with real managed clusters and VM resources, since foundation only processes ClusterPermission CRs on the hub side, so as long as there is a real hub cluster and some real ClusterPermissions created. 

Definition of Done for Engineering Story Owner (Checklist)

• ...

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.