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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchTo make KubeCon + CloudNativeCon North America 2026 useful for your SRE work, start with a production problem your team needs to solve—not a list of talks to collect. Then use the schedule, project communities, maintainers, and other operators to explore it across observability, incident response, networking, security, platform engineering, scaling, and operations.
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); seating is first come, first served. Check the official schedule for current sessions and room details, which may change.
Start with the reliability problem you want to investigate
Before choosing sessions, identify the issue that would make the conference week most valuable to your team. A specific concern gives you a practical filter for the program and helps you decide which conversations are worth having.
- 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?
Pick one primary question and, if useful, a secondary one. You do not need to cover every reliability topic in four days; you need to leave with useful approaches and questions to test against your environment.
#1 Best Overall
Choose a Monday co-located event that fits the problem
CNCF’s guide describes Monday’s CNCF-hosted co-located events as full- or half-day options for attendees with an All-Access Pass. Confirm current program and pass eligibility before planning around one.
| Option named in CNCF’s guide | Best fit when your question involves |
|---|---|
| Observability Day | Telemetry and observability; the guide calls it a natural starting point for SREs. |
| CiliumCon | Networking, security, performance, or observability. |
| FluxCon | GitOps and continuous delivery. |
Treat these as focus choices, not automatic recommendations: pick the event that matches your production concern, then verify its current schedule and access terms through the CNCF SRE guide.
Build a cross-track main-conference agenda
Operations + Performance is a reasonable starting point, but SRE work rarely stays inside one track. Follow your problem into sessions on observability, connectivity, security, platform engineering, and the Maintainer Track. Project communities at the event can add context that a talk alone may not provide.
Match the layer to the symptom
- Incident context or slow diagnosis: look at observability and incident-response sessions, including work that connects telemetry with deployment, service, and ownership context.
- Network-related reliability or migration risk: consider connectivity and Cilium-related sessions, especially if networking changes are part of your operating environment.
- Scaling pressure: search for autoscaling and performance topics, including the scheduled KEDA session.
- Delivery-related toil or uncertainty: look at GitOps, continuous delivery, and platform engineering, including Flux-related topics.
- Security-related reliability constraints: include security sessions where they intersect with the systems and responsibilities your team owns.
Use session titles as leads, not proof
The published program includes sessions whose titles describe a cascading deletion affecting 39 clusters and an eight-minute clock skew, as well as a zero-downtime CNI migration. Those figures and outcomes are claims in session titles or descriptions, not independently audited findings. Use them to identify talks that may be relevant, then assess the presenters’ evidence and operating context for yourself.
The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Other scheduled topics include OpenTelemetry Collector transformations and autoscaling with KEDA. A Nubank session title claims a pipeline running at “16 Billion Spans/Hour”; that is the session’s stated scale, not a general performance benchmark. The schedule also lists “The SRE Is Not Dead: What AI Taught Us about Missing Context in Kubernetes Incident Response,” with a presenter description involving OpenTelemetry, Argo CD, Prometheus, Grafana, and Backstage, plus a HolmesGPT troubleshooting session. These are planned talks and presenter descriptions, not independent product evaluations.
Follow projects your team already operates
Prioritize sessions and conversations about tools and dependencies present in your production stack. CNCF points attendees toward Maintainer Track sessions and the Project Pavilion, with examples including OpenTelemetry, Prometheus, KEDA, Flux, Cilium, etcd, OpenCost, and Linkerd. A project’s presence in the guide is not a recommendation to adopt it; relevance depends on your environment.
Rank #4
Prepare questions that connect the project to your day-to-day work:
- What implementation choices tend to create operational trouble?
- Which changes or roadmap items could affect your deployment?
- What technical challenges are maintainers focused on?
- How does the project behave in the edge case or failure mode your team cares about?
Use a talk for an overview, then use maintainer or operator conversations to probe the details that matter to your deployment. Bring enough context to make the question concrete—such as the component involved, the symptom, and what you have already tried—without sharing sensitive production information.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteBest Value
Leave room for conversations and follow-up
Do not fill every time slot. CNCF emphasizes direct troubleshooting conversations with maintainers and other operators as part of the in-person value: you can ask about environment-specific edge cases and compare operational experience. Unscheduled time gives you room to pursue a useful answer when a session raises a new question.
The guide also notes that scheduled recordings will be available after the event. That makes it practical to prioritize live sessions and conversations that benefit most from being there, then use recordings to catch talks that conflict. Check the official program for recording availability and details.
Turn the week into a testable SRE takeaway
Keep notes organized around your original production question, not just the sessions you attended. For each useful idea, record the problem it addresses, the conditions under which it might apply, and what your team would need to verify before changing production practice.
- Pattern: What approach to observability, incident response, performance, telemetry cost, autoscaling, networking, GitOps, or resilience is worth investigating?
- Context: What workload, architecture, or operational assumptions did the presenter or operator describe?
- Test: What small, safe experiment or follow-up question could establish whether it applies to your systems?
- Owner: Who will take the question back to the team and decide whether to pursue it?
A useful outcome is a short list of patterns and questions your team can evaluate—not a shopping list of tools or a claim that one conference session settles a production decision.
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.
