OpsCanary
kubernetesschedulingPractitioner

Harnessing CoHDI: Transforming Kubernetes with Composable Disaggregated Infrastructures

5 min read CNCF BlogJul 29, 2026Reviewed for accuracy
Share
PractitionerHands-on experience recommended

The introduction of CoHDI marks a significant shift in how we think about Kubernetes and resource management. By enabling a community-driven, standards-based ecosystem for next-generation architectures, CoHDI addresses the growing need for flexibility in resource allocation within Kubernetes environments. This is especially crucial in production settings where resource demands can fluctuate rapidly.

CoHDI operates through Dynamic Resource Allocation (DRA), which facilitates the host-level dynamic attachment and detachment of PCIe devices on Kubernetes nodes. This is achieved through three core components: the Composable-DRA-Driver, the Dynamic-Device-Scaler, and the Composable Resource Operator. The Composable-DRA-Driver works in tandem with the Dynamic-Device-Scaler to scale devices based on Pod requests without requiring OS reboots. Meanwhile, the Composable Resource Operator dynamically manages the attachment and detachment of hardware resources by leveraging the external API of the CoHDI manager. This integration with Kubernetes’ existing architecture allows for seamless management of disaggregated resources.

In production, you'll need to be aware of how these components interact and the potential for increased complexity in your infrastructure. The launch in March 2025 means that while the technology is cutting-edge, it may still have some rough edges. Ensure you test thoroughly in staging environments before rolling out to production. Keep an eye on updates from the community as this technology matures and evolves.

Key takeaways

  • Leverage Dynamic Resource Allocation (DRA) for efficient resource management.
  • Utilize the Composable Resource Operator to dynamically manage hardware resources.
  • Implement the Composable-DRA-Driver and Dynamic-Device-Scaler for seamless device scaling.

Why it matters

This evolution in Kubernetes allows for more efficient use of resources, reducing waste and improving application performance in dynamic environments. It directly addresses the challenges of scaling in modern cloud-native applications.

When NOT to use this

The official docs don't call out specific anti-patterns here. Use your judgment based on your scale and requirements.

Want the complete reference?

Read official docs

Test what you just learned

Quiz questions written from this article

Take the quiz →
Better StackSponsor

Unified observability — logs, uptime monitoring, and on-call in one place. Used by 50,000+ engineering teams to ship faster and sleep better.

Try Better Stack free →

Get the daily digest

One email. 5 articles. Every morning.

No spam. Unsubscribe anytime.