Check your inbox for a confirmation email where you can adjust your preferences and even join additional groups. Welcome to another edition of Road to KubeCon , your source for everything Kubernetes and cloud-native as we count down the days to KubeCon + CloudNativeCon NA , happening November 9-12 in Salt Lake City, Utah. This week, we take a look at the state of agent harnesses and what needs to evolve. We also feature HPE's thoughts on Kubernetes visibility, more sci-fi agentic DevOps, and an impressive scheduler that shows Kubernetes' default scheduler who's the boss of GPU utilization.
That plus news from CNCF: what to expect at this year's ArgoCon, a great opportunity to improve your open source project's security hygiene, Atlassian's stack for slashing event-to-metric latency, and a special gift for TNS readers. Getting Kubernetes running is a milestone. Knowing who owns the next upgrade, the access request, or failed recovery is an ongoing journey. This week, we published " A live Kubernetes cluster can still have an ownership gap ," the second installment in Chris J. Preimesberger's four-part, HPE-sponsored series.
It examines how platform and application teams divide responsibilities after launch, from configuration drift and security policies to upgrade validation and recovery drills. A healthy cluster doesn't necessarily mean a healthy application - and someone needs to own that gap. Hewlett Packard Enterprise (HPE) is a presenting sponsor of Road to KubeCon. HPE Software helps IT organizations modernize infrastructure, streamline operations, and accelerate AI initiatives across hybrid, multi-vendor environments.
Part one explores Kubernetes self-service : how developers can get approved environments without waiting through ticket queues, while platform teams retain responsibility for access, costs, and lifecycle controls. Together, the articles ask a practical question: How do you give developers more independence while making operational accountability clear? Next, the series turns to diagnosing slow applications when Kubernetes looks healthy, then to measuring AI inference performance. Both will explore the visibility teams need as their workloads become more demanding on the road to KubeCon.