Infrastructure engineers operate at the bustling crossroads of modern cloud environments. Their responsibilities span a vast landscape: orchestrating containerized applications, connecting complex networks, providing persistent storage, and constructing platforms that remain both usable and secure. In recent years, that roster has expanded further to include supporting GPU-intensive, artificial intelligence, and autonomous agent workloads.
Reflecting this reality, the upcoming annual gathering of cloud native professionals features a curriculum as broad as the challenges these teams face. Attendees will navigate tracks covering platform engineering, operations and performance, connectivity, data processing and storage, security, AI infrastructure, and project maintenance.
For infrastructure professionals, the true value of the event lies in the ability to compare architectures and operating models with industry peers. It is a chance to hear how other organizations are solving production problems at massive scale, and to engage directly with the developers building the tools that underpin their daily work. Infrastructure decisions are rarely made in the abstract; they are driven by platform limits, scaling challenges, migration deadlines, and budget constraints. Bringing one of these real-world problems to the event is the best way to pressure-test assumptions and find practical solutions.
Before diving into the main agenda, attendees can participate in several intensive co-located events. A day dedicated to platform engineering explores the real-world hurdles of building internal developer platforms. Another deep-dive focuses on cloud networking, observability, and security using modern data path technologies. There are also specialized days for infrastructure-as-code practitioners and teams operating GitOps-based continuous delivery environments. With so many compelling options, selecting just one is the first challenge.
During the main sessions, look for talks that bridge high-level architecture decisions with the gritty reality of running infrastructure at scale. Topics will cover autoscaling, GitOps workflows, GPU scheduling, multi-cluster management, access control, and production reliability. As AI infrastructure remains a dominant theme throughout the agenda, it is important to remember that this does not require learning an entirely new paradigm. The core questions remain unchanged: Where does the workload execute? How does it scale? How is it secured? How is it observed? The AI-focused sessions will demonstrate how familiar infrastructure principles are being adapted for a new generation of compute-intensive workloads.
Beyond the lecture halls, the project exhibition area offers an invaluable opportunity to step away from documentation and speak directly with upstream maintainers. Here, you can discuss architecture choices, deployment patterns, upcoming features, and the specific production issues you are encountering. This is where the most candid conversations happen, addressing what actually broke, what changes were made, and what would be done differently at twice the scale.
By the end of the week, attendees should walk away with concrete reference points for multi-cluster and platform architecture decisions, a clearer understanding of the tradeoffs behind infrastructure automation, and actionable strategies for integrating AI workloads without sacrificing core reliability and security practices. Whether your focus is on production operations, developer platform engineering, or shaping the open-source projects your organization depends on, there is a specific track to guide your journey.
### Frequently Asked Questions
**Who is this event most beneficial for?**
This gathering is ideal for infrastructure engineers, platform teams, site reliability engineers, and technical leaders who are responsible for managing containerized environments, networking, storage, and now, AI hardware at scale. It also benefits those who maintain or influence the open-source projects their platforms rely on.
**Why are the pre-conference days important?**
The pre-conference deep dives allow attendees to intensely focus on a single technology or methodology—such as internal developer platforms, specific networking tools, or GitOps—before the main conference dilutes the focus with broader, multi-topic sessions. It is an excellent way to get up to speed on a specific stack quickly.
**How do traditional infrastructure principles apply to AI workloads?**
Despite the shift toward GPU and AI-specific hardware, the fundamental challenges of infrastructure remain the same. Workloads still need to be scheduled, scaled, secured, and observed. The AI sessions explore how these established principles are being applied to the unique resource demands and latency requirements of machine learning models.
**What is the best way to prepare for the event?**
The most effective preparation is to identify a specific, active challenge your team is facing—whether it is a scaling bottleneck, a migration hurdle, a cost constraint, or a security policy dilemma. Use the sessions and maintainer discussions to pressure-test that specific problem and bring back tangible solutions.
### Conclusion
As infrastructure engineering grows increasingly complex, bridging the gap between theoretical technology and real-world, large-scale production operations becomes essential. This summit provides the unique environment to do exactly that, fostering connections between practitioners, upstream developers, and peers facing similar challenges. By engaging across multiple tracks and leveraging the expertise available in the exhibition hall, infrastructure teams can return to their organizations with the strategies and references needed to navigate their next major architectural decisions.
Thank you for reading
