Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Clear out junk files and repair common Windows errors3Fix the driver behind crashes, sound loss and screen glitchesBuild your KubeCon + CloudNativeCon North America 2026 agenda around a real production problem—not a race to attend every SRE-adjacent talk. The event runs November 9–12 in Salt Lake City, Utah, and reliability topics span operations, observability, networking, security, platform engineering, scaling, and incident response. Start with the place your team loses time or confidence, then use sessions and conversations to investigate it.
When and where is KubeCon + CloudNativeCon North America 2026?
The conference is scheduled for November 9–12, 2026, in Salt Lake City, Utah. The official schedule displays times in Mountain Standard Time (UTC−7), and seating is first come, first served. Check the official schedule near the event for current session, room, and timing details, since logistics can change.
As an Amazon Associate I earn from qualifying purchases.
Start with the production problem you need to understand
Before choosing sessions, write down one recurring incident, source of toil, reliability constraint, noisy system, or scaling challenge that matters to your team. Use it as a filter: a useful session should help you understand the problem, expose a relevant operational pattern, or give you a better question to take to a maintainer or another operator.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minute- 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?
You do not need to solve all four questions. Pick the one with the greatest operational consequence and let it guide your week.
#1 Best Overall
Decide whether a Monday co-located event fits
CNCF’s guide describes Monday co-located events as full- or half-day options for attendees with an All-Access Pass. Match the focus to your problem, and confirm current program and pass eligibility before planning around one.
| Option | Best fit |
|---|---|
| Observability Day | Telemetry, instrumentation, and observability questions; CNCF presents it as a natural starting point for SREs. |
| CiliumCon | Networking, security, performance, or observability concerns related to Cilium. |
| FluxCon | GitOps and continuous delivery concerns related to Flux. |
Search across tracks, not just Operations + Performance
SRE work crosses system boundaries, so the Operations + Performance track is a starting point rather than a complete agenda. CNCF’s guide points reliability practitioners toward Observability, Connectivity, Security, and Platform Engineering sessions, as well as Maintainer Track sessions and CNCF project communities.
The 2026 program includes talks whose titles or descriptions address varied operational concerns: a cascading deletion affecting 39 clusters, an eight-minute clock skew, autoscaling with KEDA, OpenTelemetry Collector transformations, and a zero-downtime CNI migration. These are scheduled session topics and presenter claims, not independently audited case-study findings. Treat them as clues for deciding what to investigate, not proof that a particular technique will work in your environment.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →For incident response and missing context
The schedule lists “The SRE Is Not Dead: What AI Taught Us about Missing Context in Kubernetes Incident Response.” Its description says the presenters combined OpenTelemetry, Argo CD, Prometheus, Grafana, and Backstage for incident context. That is a scheduled talk description, not an independent product evaluation. The program also lists a HolmesGPT troubleshooting session.
For tracing and telemetry
A Nubank session is titled “Tracing at Scale: Running a 16 Billion Spans/Hour Pipeline at Nubank.” The figure is a claim in the session title, not a separately verified performance result. Use the talk to assess what questions its approach raises for your own telemetry volume, cost, and operational needs.
Use maintainers and project communities to get specific
Follow projects already present in your production stack instead of collecting names for a future tool-shopping list. CNCF suggests Maintainer Track sessions and Project Pavilion conversations; examples in its guide include OpenTelemetry, Prometheus, KEDA, Flux, Cilium, etcd, OpenCost, and Linkerd.
Rank #4
Bring a concise, environment-specific question. Ask how a feature is implemented, what changes are coming, which technical challenges remain, or how maintainers think about a failure mode you have encountered. A focused question is more useful than asking for a general roadmap recap.
Compare sessions by operational value
When two sessions compete for the same slot, assess them against the problem you chose rather than choosing by track name alone.
Best Value
- Problem: Does the talk address your incident pattern, toil, reliability constraint, or scaling concern?
- Layer: Is it about telemetry, incident response, networking, security, platform engineering, or delivery?
- Evidence type: Is the session offering operational experience, hands-on practice, or roadmap context? A title claim is not the same as independently verified evidence.
- Stack relevance: Is the project already in your environment, or would the session answer a concrete decision you need to make?
- Practical fit: Do the time, room, seating, and any pass requirements work for your plan?
Leave room for conversations and follow-up
Do not fill every available slot. CNCF’s guidance treats direct troubleshooting conversations with maintainers and other operators as part of the in-person value: they let you ask about environment-specific edge cases and compare operational experience. Keep a few concrete questions ready, but leave room for useful conversations you could not schedule in advance.
The guide also says scheduled recordings will be available after the event. That makes it reasonable to prioritize a conversation or a session that directly fits your production problem over trying to be in every room. Confirm recording availability and details through the event’s official channels.
Turn the week into a testable next step
Leave with patterns and questions to test, not merely a list of technologies to adopt. Depending on your focus, that may mean a new approach to observability or incident response, a way to investigate telemetry cost, a better autoscaling or networking question, a GitOps practice to evaluate, or a resilience pattern to discuss with your team.
For each useful idea, capture the problem it addresses, the conditions it assumes, and the smallest safe way to evaluate it at home. That keeps a conference insight tied to an operational need rather than turning it into an unexamined change request.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
