KubeCon for First-Timers: What Actually Matters (And What Doesn't)
This is our first KubeCon: Amsterdam, 12,000+ people, dozens of tracks, hundreds of sessions. And a schedule that looks like it was designed to test your attention span, ideally before your second Dutch coffee of the morning.
If you're attending for the first time too, you're probably wondering the same things we were: How do you not get overwhelmed? What actually matters?
We turned our prep notes, plus advice from experts in the industry who've been here before, into a practical guide to navigating your first KubeCon.
Yes, KubeCon Is Bigger Than You Think
What do you think when you look at the KubeCon schedule for the first time? It feels overwhelming: there's the opening keynote, platform engineering tracks, security tracks, AI infrastructure tracks, GitOps, networking, and more, all happening at the same time.
That's exciting, but also intimidating.
A first-time attendee on Reddit summed it up perfectly:
I'm super excited but also a bit overwhelmed looking at the schedule.
That mix of excitement and overwhelm is common. It's almost a rite of passage.
We asked Juliano Costa, Developer Advocate at Datadog & CNCF Ambassador, what's his advice to people attending their first KubeCon. Here's what he shared:
I've heard it's your first KubeCon? First of all, it's huge. You will probably feel overwhelmed at some point, and that's completely normal. A common mistake I see first-timers make is trying to 'hug the whole world,' as Brazilians would say.
Keep calm, focus on what genuinely interests you, and go deeper there. Plan your schedule ahead of time and have backup sessions since rooms can fill up quickly. And please, don't spend your time taking pictures of slides — they will all be online. Use your time to absorb, reflect, and most importantly, connect with people.
Don't forget to go to the Project Pavilion, talk to maintainers, share your pain points, ask questions, and don't be shy. The CNCF community is incredibly welcoming. If you see me around, come and say hi!
That shift, from trying to "hug the whole world" to choosing what genuinely matters, changes the way you move through the week.
It replaces pressure with intention.
Instead of trying to max out your schedule, start with a simple shift: stop thinking about how much you might miss, and start thinking about what you're trying to get from the experience.
Because no matter how many sessions you bookmark or how many booths you visit, you won't cover it all. And you won't need to.
You will walk into rooms you didn't plan on. You'll overhear conversations that surprise you. You'll meet people whose work you only half-knew before. Those moments won't be on your schedule, but they will be some of the most meaningful parts of the week.
That's where the value of KubeCon lives: in the unexpected, the spontaneous, and the conversations you didn't expect.
What's the Best Way to Navigate the KubeCon Schedule?
After the initial overwhelm fades a little, something else takes over: you start planning.
The KubeCon schedule is impressive in a way that makes it difficult to stay restrained. Every session sounds relevant, every panel feels important. There are talks on platform engineering, GitOps workflows, security patterns, AI infrastructure, multi-cluster management, all running in parallel like a cluster under peak load.
It's easy to convince yourself that if you just configure your calendar correctly, you can schedule everything without hitting limits or that with enough careful orchestration, your personal bandwidth will auto-scale.
But unlike Kubernetes, your energy doesn't horizontally scale on demand.
And the more you try to pack into each time slot, the more likely you are to create contention: context switching between rooms, racing across halls, half-processing one idea before the next one starts deploying itself into your brain.
As Edgaras Apšega, SRE at Vinted & CNCF Ambassador and Kubestronaut, shared with us:
The biggest mistake first-timers make at KubeCon is trying to attend talks all day, every day. It's tempting, but you'll miss a huge part of what makes the event valuable. Instead, balance your time between key presentations and the expo floor, talk to vendors, explore what's trending, and have real conversations about how companies are solving problems and building in the cloud-native ecosystem. KubeCon is ultimately about community and shared ideas. Prioritize the sessions where you want to ask questions live, and remember, you can always catch the rest on YouTube later.
While there's something comforting about filling every slot in your calendar, by the second afternoon, that tightly packed schedule can start working against you. You're moving quickly between rooms, trying to absorb complex material back-to-back, barely leaving space to process what you've just heard. The experience becomes transactional instead of meaningful.
A more sustainable approach is quieter: choose a few sessions each day that genuinely matter to you. Not the ones that look popular, or what everyone else says are "must-see."
The ones that align with what you're curious about right now, where you might want to stay afterward and speak to the presenter. The ones where being physically present actually adds something.
Where the Real Value Happens: Sessions, Hallway Track, or Expo Floor?
Now, if you've left space in your schedule, something interesting starts to happen.
You begin to notice what's happening between the sessions, the traffic that isn't captured in the official agenda.
The conversations that continue long after a talk ends. The small groups gathered around a whiteboard near the Project Pavilion, sketching architectures like they're debugging a controller loop. The engineer who stays back to ask one more question because something didn't quite reconcile. The maintainer who's no longer just a GitHub avatar, but a real person explaining why something behaves the way it does.
This is what people mean when they talk about the "hallway track."
It sounds informal, and it is. But it's also where a surprising amount of insight lives. Not the polished version that makes it into slides, but the lived experience version. The "this is what actually broke in production" version. The "here's how we're thinking about it internally" version.
Many repeat attendees say the same thing when they reflect on their first KubeCon: some of the most meaningful lessons surprisingly didn't come from the slides or demos, but from conversations over lunch, or standing in line for coffee, from impromptu technical debates that started with a simple, "How are you handling this in your cluster?"
As Maryam Tavakkoli, Lead Cloud Engineer at RELEX Solutions & CNCF Ambassador, shared with us:
If I had to give a first-timer one thing to prioritize at KubeCon, it would be people over sessions. You don't need to attend every talk that sounds interesting; pick a few that truly matter to you and spend the rest of your time connecting. Some of the most valuable insights, ideas, and opportunities come from hallway conversations and spontaneous meetups.
That perspective changes how you move through the event.
The expo floor, officially the Solutions Showcase, can feel overwhelming at first. Yes, there's vendor noise. Yes, there's swag. But there are also engineers behind those booths who build the tools you use every day. If you arrive with real questions instead of casual curiosity, the conversations become far more interesting.
And then there's the Project Pavilion.
If you're running Kubernetes, Flux, Argo, or any CNCF project in production, this is where you bring your real-world questions: the "we hit this edge case under load" questions. The "why does this behave differently in our cluster" questions. The kind of things you normally only ask in Slack threads or GitHub issues.
Those conversations won't appear on your calendar or show up in your bookmarked list of sessions, but they are often the moments people remember long after the slides are forgotten.
Networking for People Who Prefer YAML
For many engineers, the word "networking" is enough to raise the pressure.
Most of us would rather debug a flaky production issue than initiate small talk with a stranger.
And that's fair.
But that's rarely what KubeCon feels like once you're actually there, even if you think "My small talk works best in YAML."
No one is walking around asking for a rehearsed summary of your career. They're asking, "How are you handling this in production?" or "Have you tried this approach?" The conversations are technical. Practical. Specific.
If you're more introverted, you don't need to suddenly become someone else for four days.
Treat it less like networking and more like debugging a distributed system: start with one thread, or one question that actually matters to you. If there's a signal, the conversation deepens. If there isn't, that's fine too, no awkward obligation to force it.
Some of the best exchanges happen because two people care about the same weird edge case in Kubernetes and decide to talk about it for ten minutes.
Energy, Walking, and Practical Realities
There's a part of KubeCon that doesn't show up in the conference app.
KubeCon = (sessions + conversations + walking²) ÷ sleep
Well, you only realize the walking² part once you're there.
You don't see it when you're planning your schedule. It only becomes real once you're there, somewhere between your third conversation of the morning and the moment you realize you've been standing for most of the day.
KubeCon is energizing, but it's also physically demanding in ways that are easy to underestimate.
The venue is large, sessions are spread across halls, conversations rarely end exactly when you expect them to. You'll also move more than you planned to or stand longer than you thought you would. And your brain will be processing a constant stream of new ideas, tools, and perspectives.
It's a lot.
As Divine Odazie, CEO at EverythingDevOps & CNCF Ambassador, shared with us:
As a first timer, I would advise you to prioritize networking over trying to attend all the talks. Remember there are going to be recordings on YouTube. Check out Network Nook during lunches, great way to meet people who want to network.
What to avoid? Please avoid any shoe or footwear that isn't very comfortable. KubeCon involves a lot of standing, walking, and sometimes running 😅 Joking. But travel with your best comfortable shoes. Your legs would thank you.
Comfortable shoes might sound like a small detail, but by day two, they won't feel small at all.
Sometimes the most strategic choice you can make is stepping outside for a few minutes, sitting down without an agenda, or skipping a session to reset.
Co-Located Events and Workshops
Wait, did we even mention that KubeCon technically starts before it starts?
Before the main conference officially begins, there's already a different kind of energy building. Monday is dedicated to co-located events, and honestly, we almost overlooked them at first.
They're smaller, topic-focused gatherings that run before the main KubeCon schedule fully takes over and don't always get the same spotlight as the keynotes, but the more we spoke to people who've attended before, the more we heard the same thing: these sessions can end up being some of the most valuable time of the week.
If you're planning to attend co-located events, it's worth checking registration details early. Many of them require an All-Access pass and some fill up quickly. You can review registration options here.
The full schedule, including co-located sessions and workshops, is available on Sched, which is also where you can build your personal agenda.
CNCF also publishes an overview of official co-located events and sponsor-hosted co-located sessions.
Tip: Many co-located sessions have limited seats. Register early.
We also recommend joining CNCF Slack, good for finding meetups and real-time updates, and following the hashtags #KubeCon and #CloudNative for live updates and side events.
During the main conference days, workshops offer a similar kind of depth: they're interactive, slower-paced, and usually leave you with something tangible you can bring back to your team. If you learn best by doing rather than watching, these are worth prioritizing.
And then there are the side events, which honestly deserve their own mention because they can end up being some of the most memorable parts of the week.
The evening meetups or smaller community gatherings: some are vendor-hosted, some are entirely community-driven. If networking feels intimidating in the main halls, these settings often lower the stakes. Smaller groups make it easier to speak up. You're not forcing an introduction, you're reacting to a shared topic.
Of course, you don't need to attend every side event. But if you find the right one, it can feel less like an extension of the conference and more like a room full of people genuinely thinking through the same problem you are.
How We're Approaching Our First KubeCon
After talking to people who've attended before and comparing notes internally, we realized it's not about attending the most sessions or squeezing value out of every hour. What we're looking for instead is clarity about where the ecosystem is heading and where we want to focus our energy.
One piece of advice that really stuck with us came from Koray Oksay, Kubernetes Consultant at Kubermatic, CNCF Ambassador and DevOpsDays Istanbul Organizer:
I would prioritize conversations over sessions. The talks are recorded, but the hallway discussions, chats with maintainers, and spontaneous whiteboard moments only happen there. Some of the best technical insights I gained came from chats, not stages.
I would avoid over-optimizing the talk schedule. Pick a few key talks, then invest the rest of your time in conversations: project maintainers, platform engineers running things at scale, and the people behind the tools you use every day.
So rather than chasing every track, we're choosing a few themes that genuinely matter to the work we're doing right now: GitOps tooling, multi-cluster management, developer experience, and how teams are thinking about AI in infrastructure. That focus naturally connects to how we're continuing to build and introduce Kunobi within the Kubernetes community.
As Ainhoa Aldave, from Team Kunobi, put it when we asked what she's most looking forward to:
I'm really looking forward to hearing people's pain points firsthand. What's actually challenging them right now, what gets messy in production or breaks at scale. I'm especially curious about how teams are thinking about the security implications of running agents with broad permissions in Kubernetes environments.
For me, it's about quality over quantity: fewer but deeper conversations, a handful of talks that really matter. And yes, I'm packing my best running shoes. We're ready for the marathon.
If something aligns with those areas, we'll lean in. If it doesn't, we're comfortable letting it pass. And if we leave Amsterdam with a handful of meaningful discussions and a clearer sense of where the ecosystem is heading, that will be enough.
Final Thoughts: Don't Over-Engineer Your KubeCon
Ever tried to schedule more pods than your cluster can handle?
That's what first-time KubeCon planning can feel like, as if success depends on packing every available slot and proving you extracted maximum value from the week.
It doesn't.
You'll miss a session someone later calls brilliant. You'll walk into the wrong room at least once. You might even pretend you knew where you were going the whole time.
That's part of it.
What people actually remember isn't the perfectly tuned schedule. It's the conversation that ran long, the offhand comment that made something click, the realization that other teams are debugging the same strange Kubernetes behavior you are.
You can't optimize for that. You just have to show up for it.
You can also use these resources if you've missed some talks:
- CNCF YouTube channel, recordings are published after the conference
- CNCF blog, post-event analysis and ecosystem trends
But the hallway moment where someone sketches an idea on a napkin and suddenly your architecture makes more sense? That only happens if you're there for it.
And honestly, that's enough.
If you see us wandering between halls with coffee in hand and slightly confused expressions, that's probably us doing it right.
If you'll be at KubeCon Amsterdam, reach out and let's connect. We'd love to talk about Kubernetes tooling, GitOps workflows, or whatever you're working on. Find us on LinkedIn: Juan and Ainhoa.