KubeCon + CloudNative North America 2022

Storage is always a sticky topic in Kubernetes, and all the more so when you have choices to make. When you are not using a cloud-provider's block storage, there are quite a number of options available to you. Which system should you use? In this talk, we will examine a number of the storage systems available to Kubernetes and give you tools to evaluate when it makes sense for you to use which. We look at performance, reliability, sustainability, cost, and many other factors to arm you with enough information to make the choice for yourself.

Many CNCF participants use bees as logos (e.g. eBPF, Cilium, GiantSwam, Honeycomb). This is no coincidence; the two worlds have more in common than you might think. Honey bees are social animals which operate as a distributed system. As experienced beekeepers and cloud-native engineers, the similarities between bees and Kubernetes are fascinating. Bee hives autoscale, self-heal, have message passing mechanisms, service discovery, and RBAC. For bee colonies, these are fundamental processes which must be cost-effective. This talk is an introduction to the fascinating world of honey bees, explains how bees have solved problems we face on a daily basis as Kubernetes users and gives an outlook on features that are missing from Kubernetes which bees support today.

“How can I get started?” is a common refrain heard from newcomers wanting to enter open source. This talk is the exact opposite - where you shouldn't invest your efforts while getting started. Being a new contributor to open source can be intimidating because you don’t know exactly what is helpful and what could hurt the community and frustrated maintainers. While a part of this gap can be attributed to the choose-your-own-adventure nature inherent to open source, there's already tons of material on how to get started technically. What nobody actually shines light on is the cultural dynamics. With this talk, the speakers aim to retell their experience and list common pitfalls almost everyone (including the speakers!) have made. This isn’t just about the right way to make a PR. The hardest, and most rewarding part, of any community is the people. The audience will learn how to engage in open source to ensure that the community they join will continue to be happy and healthy.

Setting the proper limits and requests to a Kubernetes cluster is one of the most challenging tasks engineers have to face. Not doing this could have critical consequences, like outages or astronomical cloud bills. Sometimes, when engineers don't have the full picture of the cluster they're working on, they tend to use more resources than actually needed for their workloads. This is called the "greedy developer" problem. To avoid this, you'll have not only to identify the unused resources, containers without limits, or very tight ones. But also to set the right requests and limits. In this talk, Jesus and David will walk you through this process. You might have to add new nodes, or just resize your workloads. Since every cluster is different, also measure the optimizations made, to help our audience with their own clusters.

You started using Kubernetes. You are doing great! Then you figure out "hey if kubectl has colors probably it would be helpful for other people!" You go ahead, and open an issue in the Kubernetes repository, to figure out that there's another issue opened since 2016 about this! And with a lot of discussions! Yeah, it happens! But why does it take so long? Is this really necessary? In this talk, we will present to you how a new feature gets into Kubernetes and, most importantly, why it takes so long! We are going to pass through some simple scenarios to understand what is this review process, what problems were caught in some real life feature requests reviews, and also other examples of features that were promoted and now became a problem, trying to understand why they reached this status! Join us and learn a bit more about the enhancement process of Kubernetes!

Kubernetes is effectively a blank canvas which we as engineers need to compose into a shape and style that fits our needs. This nearly always starts with running software through deployments. While this can get us started, many of our high value use cases require more complex compositions. Operators provide engineers a way to extend the building blocks of Kubernetes to build higher level abstractions. These abstractions can codify complex setup requirements, standardise capabilities across an organisation, and more. An example of operators at work include the Prometheus operator. This helps teams get started with monitoring and alerting with packaging and providing sensible defaults across an array of associated tools including Prometheus (for metric gathering), Thanos (for metric retention), Alertmanager (for alerts), and Grafana (for graphing). In this workshop we will build a basic operator which will enable a hands on exploration into use cases and structures of operators in more depth.

Who has not once said the phrase:
- I sucks
- I don't know anything
- I feel like an impostor
- I don't feel legitimate to do this or do that

Some people are convinced that they do not deserve their success, despite the efforts they make to succeed. They often convince themselves that their success is not linked to their work, their personal accomplishment, but simply to luck or the work of others. In fact, they live permanently with a feeling of deception and constantly fear that someone will unmask them from one day to another. Despite my stuttering, I am a speaker, a mentor, a conference organizer and very invested in women in tech and tech communities.

In this talk, we will see what the impostor syndrome is, how it is reflected on a daily basis and we will see that it is not inevitable, on the contrary, that there are tips and tricks for the fight, overcome and improve. And I will also tell you several anecdotes that happened to me, which were very hard and which made me who I am today.

CNET is no stranger to the world of containers; having been an early adopter of Docker Swarm, we've been using containers for many years! Recently, we migrated our workloads to Kubernetes, and the CNCF ecosystem has been a core component of our tech stack. As we started our application modernization initiative, we quickly realized by utilizing tools like Prometheus, Cert-Manager, External DNS, Traefik Ingress controller, Open Policy Agent, and others, we could give our developers a robust environment. The Kubernetes-based platform is not only for Production but Development Environments as well. The consistency between environments has kept our error rates down and websites up! Let's look at the flexibility the open software platform has given our developers! Let's take a journey from the perspective of a requested change on the front door of the website! First, a Product Manager makes the request, then we can see how a developer makes the change to the codebase and how quickly we can give the product manager a sandboxed environment to validate the requested change. the whole process takes only a few minutes. All of this is possible using open technology and our cloud provider. Let us show you how these tools work together to accomplish this flexibility and scale!

You just started a new gig ? You switched laptop ? or you're new to using Kubernetes ?

From the new users of Kubernetes to the most experienced gurus, we all spend a large amount of time on the terminal* (shell).
This talk will focus on setting up your laptop and terminal, installing all the cool tools to get you productive fast with Kubernetes. It is intended for all levels of experience.

By mixing a presentation of the tooling and demos, you'll quickly see how some little tuning can increase your productivity by a large amount.

During this talk you'll learn (not limited to):
- setup your shell to connect to a Cloud K8s service
- add shortcuts to type less when using kubectl
- get a clean access to cluster's logs
- add colors to your kubectl outputs
- install and use a local k8s cluster for prototyping
- work with Containers without Docker-For-Desktop
- get to know a lot of small tools to ease the pain of maintaining a cluster, playing with yaml and more

This talk also gives access to a companion tutorial with all the commands that you can play on your laptop, during the talk or at home. 
Bring your laptop and start being more productive right now !

Join us in this adventure and impress your co-workers on your first day at work !

WARNING !

If you want to follow the talk and replicate on your own laptop, you will need a Kubernetes cluster.
it is advised to pre-install some tools so we don't burn down the WIFI of the whole conference: either Docker Desktop, Podman and Kind

For Mac OS X:
brew install podman
brew install kind
podman machine init --cpus=2 --memory=4096 --disk-size=200 --now
kind create cluster dev

Docker made container technology approachable and easy to adopt, but the recent need to replace Docker has opened up several options and complexity, which can be daunting to someone new to Container technologies. Knowing what runtime engine is suited for what type of use case is crucial in making the right choice when reaching for a replacement. In this talk, Abubakar will start with a brief primer about what the Container runtime does, the common ones available, what they have in common and what sets them apart. We will also see different use cases applicable to different container runtime engines. At the end of the talk, the listener will be better informed in choosing the most preferred runtime engine for their workload.

Every day, someone new wants to deploy their cloud-native app... then it ends up running on Kubernetes! Suddenly, all sorts of people have questions about the app and need to make changes. Developers, SREs, Product Folks, and Organization Leaders all have different needs and levels of experience with the myriad of Kubernetes resources needed for an app, so how should platform teams give folks the access they need? This session will show how the basics of Kubernetes Role-Based Access Control (RBAC) compose together to create a flexible system that lets teams work together. Come learn about: - RBAC Basics - The Details of Identity - Common Misunderstandings - RBAC's Limitations - Auditing - Useful Patterns for Real-world Implementations This session will also include some fun, relatable Live Demos! Expect to leave better equipped to support the transparent, collaborative, self-service ownership of a DevOps culture.

Most of us will spend most of the conference learning what's new in the cloud, focusing on developments from the last six to twelve months and discovering what our colleagues are working on in the future. In this talk, we'll break from that paradigm to ground ourselves by taking a look at Detroit's history and the lessons we can learn from its dominant industry. Shane will describe parallels between open source software and manufacturing, explain how lessons learned by automakers in the last century can benefit software development today, and point out potential pitfalls made by industrialists that we should seek to avoid.