feat: Introduce Kueue Headlamp plugin with a dashboard for cluster qu…

[Latish705]

Summary
This PR introduces a new plugin, @headlamp-k8s/kueue, to visualize and manage Kueue resources within Headlamp.

Changes
New Plugin: Added plugins/kueue directory.
Metadata: Configured
package.json
,
artifacthub-pkg.yml
, and
knip.json
for the new plugin.
Documentation: Added
README.md
with installation and usage instructions.
UI: Implemented basic sidebar registration for the Kueue dashboard.

[kannon92]

Excited to see this. I'm happy to help review from Kueue side once this is ready.

[kannon92]

Kueue does a UI named KueueViz. https://github.com/kubernetes-sigs/kueue/tree/main/cmd/kueueviz

It would be cool if we could figure out to reuse some of this with headlamp architecture.

[mimowo]

Thank you for driving the effort! Excited to see people building the integrations.

Do you already have some screens maybe showing the new plugin at action?

[kimminw00]

In a MultiKueue setup, if this plugin is running on the management cluster, will the resources (like ClusterQueue, Workload status) provide sufficient visibility into the usage of connected worker clusters? Or should we consider fetching additional metrics(ex. OCM) to show the complete picture?

[mimowo]

Do you maybe have already some share-able screenshots to see how this is looking / working?

[kimminw00]

Here is a screenshot of what it looks like running on my local setup.
I obtained the screenshot above by applying the following YAMLs:

# cluster-queue.yaml
apiVersion: kueue.x-k8s.io/v1beta1
kind: ClusterQueue
metadata:
  name: cluster-queue
spec:
  namespaceSelector: {} 
  resourceGroups:
  - coveredResources: ["cpu", "memory", "nvidia.com/gpu"]
    flavors:
    - name: "default-flavor"
      resources:
      - name: "cpu"
        nominalQuota: 10
      - name: "memory"
        nominalQuota: 20Gi
      - name: "nvidia.com/gpu"
        nominalQuota: 4

---
      
# resource-flavor.yaml
apiVersion: kueue.x-k8s.io/v1beta1
kind: ResourceFlavor
metadata:
  name: default-flavor

---

# local-queue.yaml
apiVersion: kueue.x-k8s.io/v1beta1
kind: LocalQueue
metadata:
  namespace: default
  name: user-queue
spec:
  clusterQueue: cluster-queue

---

apiVersion: ray.io/v1
kind: RayJob
metadata:
  name: ray-job-sample
  namespace: default
  labels:
    kueue.x-k8s.io/queue-name: user-queue 
spec:
  shutdownAfterJobFinishes: true
  entrypoint: python -c "import time; print('Hello Kueue'); time.sleep(10)"
  rayClusterSpec:
    rayVersion: '2.9.0'
    headGroupSpec:
      rayStartParams:
        dashboard-host: '0.0.0.0'
      template:
        spec:
          containers:
          - name: ray-head
            image: rayproject/ray:2.9.0
            resources:
              requests:
                cpu: 1
                memory: 2Gi
              limits:
                cpu: 1
                memory: 2Gi
    workerGroupSpecs:
    - groupName: small-group
      replicas: 1
      minReplicas: 1
      maxReplicas: 1
      rayStartParams: {}
      template:
        spec:
          containers:
          - name: ray-worker
            image: rayproject/ray:2.9.0
            resources:
              requests:
                cpu: 1
                memory: 2Gi
              limits:
                cpu: 1
                memory: 2Gi

[ashu8912]

Hii @Latish705 any update on this?? Let us know if you need help finishing this up