use all clusterqueues

[KPostOffice]

https://issues.redhat.com/browse/RHOAIENG-8102

Description

With support for multiple clusterQueues, the first element can't be relied on for total shared quota

How Has This Been Tested?

I've used the existing Cyprus UI tests to verify that empty states still work as expected and I've added a unit test to ensure that when multiple CQs are used the total quota is correctly tallied up.

To manually test create two CQs and a LQ for each CQ and make sure that the total quota in the effected UI component is the sum of the quota for both CQs

Test Impact

Request review criteria:

Self checklist (all need to be checked):

• The developer has manually tested the changes and verified that the changes work
• Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
• The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

• Included any necessary screenshots or gifs if it was a UI change.
• Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

• The developer has tested their solution on a cluster by using the image produced by the PR to main

[mturley]

Mostly LGTM, a few small things

[mturley]

You could instead get a combined array of all the resourceGroups in all the ClusterQueues by doing:

(clusterQueues || []).flatMap((clusterQueue) => clusterQueue?.spec.resourceGroups || [])

And that would just replace the original (clusterQueue?.spec.resourceGroups || []), you'd chain the existing .reduce on it and you wouldn't need your additional reduce at the end

[mturley]

This all looks good to me, but you'd want to add the logic you mentioned for filtering these by the namespace right? You could rename this to allClusterQueues and then have something like:

const clusterQueues = {
  ...allClusterQueues,
  data: allClusterQueues.data.filter((clusterQueue) =>
    localQueues.data.some(({ spec }) => spec.clusterQueue === clusterQueue.metadata.name),
  ),
};

You'll want to preserve the rest of the object you get back from useMakeFetchObject so you're still passing down loading/error state, but you can override the data being included this way.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 85.18%. Comparing base (1896f34) to head (635df77).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3540      +/-   ##
==========================================
- Coverage   85.19%   85.18%   -0.01%     
==========================================
  Files        1382     1382              
  Lines       31572    31576       +4     
  Branches     8824     8827       +3     
==========================================
+ Hits        26897    26899       +2     
- Misses       4675     4677       +2     

Files with missing lines	Coverage Δ
...stributedWorkloads/DistributedWorkloadsContext.tsx	82.85% <100.00%> (+1.60%)	⬆️
...ontend/src/concepts/distributedWorkloads/utils.tsx	100.00% <100.00%> (ø)
...orkloads/global/GlobalDistributedWorkloadsTabs.tsx	97.43% <100.00%> (ø)
...bal/projectMetrics/sections/RequestedResources.tsx	84.61% <100.00%> (ø)

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1896f34...635df77. Read the comment docs.

[mturley]

LGTM!

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mturley

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• frontend/OWNERS [mturley]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mturley]

/hold

[openshift-ci]

New changes are detected. LGTM label has been removed.