Epic Goal

MK dispatcher API

https://docs.google.com/presentation/d/10t7hWtRibr-UlNNTRytrGupjXKJWWN3gv0oLAEtr9Hc/edit?slide=id.p#slide=id.p 

Since Kueue 0.13, when a custom Dispatcher API is used, instead of creating the copy of the Workload on all clusters the MultiKueue Workload Controller only creates the copy of the Workload on the subset of worker clusters specified in the Workload's .status.nominatedClusterNames field. 

This epic is to integrate ACM Kueue Addon with MK dispatcher API. 

Why is this important?

Issue: Dynamic Local/Remote Workload Placement in MultiKueue Using Resource Flavors

https://github.com/kubernetes-sigs/kueue/issues/6118

Scenarios

Some use cases to consider:

1. Use multikueue without creating placement.
2. Use multikueue without creating placement, but want to change the dispatch order 
3. Use multikueue with placement.
4. Use multikueue with placement and want to change the dispatch order.

Acceptance Criteria

With the installation of the add-on the RHBoK operator is installed and (on the hub) the AdmissionController is deployed and ready to accept Placements.

Dependencies (internal and external)

1. RHBoK exists.

Previous Work (Optional):

1. OCM upstream: https://github.com/open-cluster-management-io/ocm/tree/main/solutions/kueue-admission-check

Open questions:

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>

OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

• 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 - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)