If your day starts with questions about reliability, performance, observability, incidents, scaling, or what is going to break next, there is no shortage of places to spend your time at KubeCon + CloudNativeCon North America 2026.

But the SRE journey does not live inside a single conference track.

Operations + Performance may be the obvious starting point, but SREs will also find relevant conversations across Observability, Connectivity, Security, Platform Engineering, Maintainer Track sessions, and the CNCF project communities themselves. View the tracks + schedule.

Here is one way to build your week. Register Today!

Why SREs should attend

Production reliability rarely fits inside one tool or team. KubeCon + CloudNativeCon puts the people building and operating the cloud native stack in the same place, making it possible to compare approaches to observability, incident response, autoscaling, networking, security, and performance with teams facing many of the same challenges.

Beyond the sessions, SREs can bring real production questions directly to maintainers and other practitioners, learn from failure stories and operational lessons, and come away with ideas they can apply to systems they are responsible for today.

Come with a production problem to solve

The strongest SRE journey starts with a problem you already care about. Before you arrive, think about the recurring incident, source of operational toil, or reliability constraint your team keeps running into. Use that problem as a filter for the week rather than trying to attend everything.

A few questions can help shape your agenda:

Where does your team lose the most time during incidents?
Which part of your stack creates the most noise, toil, or uncertainty?
What is hardest to scale or optimize without putting reliability at risk?
Which project or dependency would you most like to understand directly from its maintainers?

Start Monday by going deep

For attendees with an All-Access Pass, Monday’s CNCF-hosted co-located events offer an opportunity to spend a full or half day focused on one area.

Observability Day is a natural starting point for SREs, bringing together maintainers, operators, and end users working with technologies including OpenTelemetry, Prometheus, Fluentd, Fluent Bit, Jaeger, Thanos, Cortex, Perses, Pixie, Kepler, and Inspektor Gadget.

Depending on your day-to-day responsibilities, CiliumCon may be another option for deeper conversations around networking, security, performance, and observability, while FluxCon offers a closer look at GitOps and continuous delivery in production.

Think about the problem you spend the most time solving today and use Monday to go deeper.

Put reliability at the center of your schedule

As the main conference begins, look beyond one track when building your agenda. Sessions SREs may want to put on their radar include:

These sessions span operations, observability, networking, autoscaling, GitOps, and incident recovery, reflecting how reliability work actually happens in production.

Follow the projects behind the systems you operate

KubeCon + CloudNativeCon is also an opportunity to go directly to the communities building the technologies you depend on.

Look for Maintainer Track sessions and Project Pavilion conversations around projects such as OpenTelemetry, Prometheus, KEDA, Flux, Cilium, etcd, OpenCost, Linkerd, and other technologies in your production stack.

Maintainer Track sessions are particularly useful if you want to understand upcoming changes, implementation considerations, current technical challenges, or project roadmaps directly from the people building the software.

Leave room for troubleshooting conversations

Not every useful SRE conversation will happen in a scheduled session.

Visit the Project Pavilion. Talk to maintainers. Compare architectures with other operators. Ask someone else how they solved the problem your team has been fighting for six months.

That direct exchange is one of the biggest differences between watching a recording later and participating in KubeCon + CloudNativeCon in person.

Don’t schedule every minute

Most breakout and keynote recordings will be available after the event. The reason to be in Salt Lake City is what you can do with a session while you are there: ask the speaker about the edge case that looks like your environment, compare an incident pattern with another operator, or take a question directly to a project maintainer.

Leave some white space in your agenda for the Project Pavilion, Solutions Showcase, and the conversations that start when someone says, “We ran into that too.” Those exchanges can be just as useful as the session you originally planned to attend.

What you can take back to your team

The goal is not to leave with a list of tools to buy. It is to leave with stronger patterns, better questions, and a clearer sense of what is working for other teams operating cloud native systems in production.

By the end of the week, you may have:

New approaches to observability, incident response, performance, and telemetry cost
Ideas to test around autoscaling, networking, GitOps, and production resilience
Direct context from maintainers about project roadmaps and implementation tradeoffs
Peers you can continue comparing notes with after the conference

Where does the SRE journey go next?

SREs will probably see significant overlap with our Infrastructure Engineer Journey, especially around platform engineering, networking, scaling, and cluster operations.

And if you have ever filed an issue, helped debug a project, contributed documentation, or wanted more influence over a technology you rely on, take a look at the Maintainer Journey too.

Your next step in cloud native might be closer than you think.

Join us in Salt Lake City and start building your KubeCon + CloudNativeCon North America journey.

Don’t forget to register for KubeCon + CloudNativeCon North America 2026.