Link: https://youtu.be/AjvwG53yLMY
https://go.dok.community/slack
https://dok.community/
ABSTRACT OF THE TALK
Stateful workloads are the heart of any application, yet they remain confusing and complicated even to daily K8s practitioners. That’s why many organizations shy away from migrating their data - their prized possession - to the unfamiliar stateful realm of Kubernetes.
After meeting with many organizations in the adoption phase, I discovered what works best, what to avoid, and how critical it is to gain confidence and the right knowledge in order to successfully adopt stateful workloads.
In this talk I will demonstrate how to optimally adopt Kubernetes and stateful workloads in a few steps, based on what I’ve learned from observing dozens of different adoption journeys. If you are taking your first steps in data on K8s or contemplating where to start - this talk is for you!
BIO
- A Developer turned Solution Architect.
- Working at Komodor, a startup building the first K8s-native troubleshooting platform.
- Love everything in infrastructure: storage, networks & security - from 70’s era mainframes to cloud-native.
- All about “plan well, sleep well”.
KEY TAKE-AWAYS FROM THE TALK
- Understand how critical stateful workloads are for any system, and that the key challenges to migrating it to Kubernetes are knowledge and confidence.
- How to build the foundational knowledge required to overcome adoption challenges by creating a learning path for individuals and teams.
- How to gain confidence to run stateful workloads on Kubernetes with support from the community (and yourself!)
4. Drum & Bass - it all comes down to stateful
● App DBs & queues are the
most critical infrastructure for
any organization
● Most applications rely on
stateful data
5. The impact of Stateful
Minor Errors
Unavailable application
Severe Downtime
DATA LOSS
High possibility
Low impact
Low possibility
Extreme impact
6. The impact of Stateful
Minor Errors
Unavailable application
Severe Downtime
DATA LOSS
High possibility
Low impact
Low possibility
Extreme impact
7. The key challenges with Kubernetes
Lack of knowledge/expertise
“Can’t read notes”
Lack of confidence/fear
“The stage fright”
Lack of instruments/tools
Lack of band members
8. Why do it anyway?
● Cost
○ Managed vs unmanaged
○ Resources footprint
○ Licences
● Multi-Cloud
● K8s standardization
○ No VMs until x
● 3rd party modernization
○ New DB/Queues
○ Automated operations
● Self-hosted / on-prem
● Your product is being deployed on hosted clusters