The Cloud Native Computing Foundation (CNCF), which builds sustainable ecosystems for cloud native software, announced that Broadcom has upgraded its membership to Platinum—reinforcing the company’s mission to advance cloud native technologies that help organizations build resilient infrastructure for the...

The vendor tied the ‘expanded investment in CNCF’ to ‘its ongoing commitment to open-source collaboration’

KubeCon + CloudNativeCon India 2026 brought the cloud native community to Mumbai on June 18-19. For LitmusChaos, this was not just another conference. It was one of our most significant events to date. We walked away...

Collaboration with CNCF reflects Broadcom’s continued investment in open source innovation, cloud native resilience and the technologies powering the next generation of AI workloads Key Highlights SAN FRANCISCO, California  — July 16, 2026 — The Cloud...

Running large language model (LLM) workloads in-house is one of several patterns teams adopt alongside managed API services. Managed API services are convenient and well suited to many workloads. Self-hosting is a complementary option that some...

The CNCF Technical Oversight Committee (TOC) has voted to accept HAMi as a CNCF incubating project.  About HAMi Modern AI infrastructure teams run into the same problem over and over: expensive GPUs often sit fragmented and...

For application teams, databases should feel like a solved problem. A team needs PostgreSQL, MariaDB, Redis, or another data service, submits a request, receives credentials, and starts building. In practice, the experience is rarely that simple....

The countdown is officially on. In just a few weeks, the cloud-native ecosystem meets in Yokohama for KubeCon + CloudNativeCon Japan 2026. Taking place on Tuesday, July 28 from 09:00 – 12:30, KeycloakCon Japan brings together...

Jonathan Bryce, Executive Director of CNCF, discusses cloud-native AI infrastructure, GPU optimisation, digital sovereignty, open source, OpenStack, and why enterprise AI will increasingly rely on proprietary, domain-specific models.

When we first started building kagent, we didn’t run every agent in its own Kubernetes Pod, Service, and ServiceAccount. Instead, agents were simply executed inside the kagent runtime. It was the simplest architecture possible: one runtime...