Skip to content

IBM/composable-resource-operator

View on GitHub ↗Related repositories →

Proof Of Concept showcasing composable GPUs in Kubernetes

active 2024-03-112025-03-10 (UTC)

Complete coverage26,392 / 26,392 hourly files (100%) · 2 absent upstream2023-08-152026-08-18 (UTC)
Events
55
Pushes
3
Pull requests
2
Issues
12
Stars
12
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 365 days from 2024-03-11 to 2025-03-10. Pushes: 3 total, peak 2 in a day. Pull requests: 2 total, peak 1 in a day. Issues: 12 total, peak 4 in a day. Comments: 18 total, peak 2 in a day. Stars: 12 total, peak 3 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
mgazz16317
hase112810005
zhouhao33001
fj-zhang-lei3003
sshukun2001
gaoaF2001
christian-pinto1010

Recent activity

Latest issues, pull requests and releases

  • Issue comment#11gaoaF2025-03-10 07:38
    Discuss the applicability of CdiProvider API to Sunfish
  • Issue#11gaoaF2025-03-10 07:36
    Discuss the applicability of CdiProvider API to Sunfish
  • Issue comment#10zhouhao32025-01-08 01:16
    Managing GPU Resources directly connect on the Worker Nodes and cannot be removed
  • Issue#10zhouhao32025-01-08 01:16
    Managing GPU Resources directly connect on the Worker Nodes and cannot be removed
  • Issue comment#10mgazz2025-01-07 10:22
    Managing GPU Resources directly connect on the Worker Nodes and cannot be removed
  • Issue#10zhouhao32024-12-24 03:01
    Managing GPU Resources directly connect on the Worker Nodes and cannot be removed
  • Issue comment#8fj-zhang-lei2024-09-24 07:51
    Use-case: Multiple composable resource operators
  • Issue#9mgazz2024-09-23 15:16
    Use-case: not enough resources to satisfy a ComposabilityRequest
  • Issue#8mgazz2024-09-23 13:43
    Multiple composable resource managers installations.
  • Pull request#7mgazz2024-09-23 12:47
  • Issue comment#6hase11282024-09-19 01:52
    Define a policy to handle the creation of multiple ComposabilityRequests targeting the same node
  • Issue comment#6fj-zhang-lei2024-09-18 04:34
    Define a policy to handle the creation of multiple ComposabilityRequests targeting the same node
  • Pull request#7christian-pinto2024-09-05 08:58
  • Issue comment#6hase11282024-09-05 08:10
    Define a policy to handle the creation of multiple ComposabilityRequests targeting the same node
  • Issue comment#6fj-zhang-lei2024-09-05 05:31
    Define a policy to handle the creation of multiple ComposabilityRequests targeting the same node
  • Issue#6mgazz2024-09-04 12:03
    Define a policy to handle the creation of multiple ComposabilityRequests targeting the same node
  • Issue comment#5hase11282024-06-28 13:32
    Improve the data format in CRD(ComposabilityRequest)
  • Issue comment#5mgazz2024-06-21 13:30
    Improve the data format in CRD(ComposabilityRequest)
  • Issue comment#5hase11282024-06-19 05:17
    Improve the data format in CRD(ComposabilityRequest)
  • Issue comment#3hase11282024-06-19 04:51
    Add vendor specific CDI client
  • Issue comment#3mgazz2024-06-18 08:17
    Add vendor specific CDI client
  • Issue comment#5mgazz2024-06-18 08:16
    Improve the data format in CRD(ComposabilityRequest)
  • Issue#5hase11282024-06-17 05:34
    Improve the data format in CRD(ComposabilityRequest)
  • Issue#4hase11282024-06-17 05:26
    Add compatibility with DRA
  • Issue#3hase11282024-06-17 05:23
    Add vendor specific CDI client

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 12 stars here means stars gained during the window, not the repo's star count.