Anti-patterns for Kubernetes Operators

on YouTube ↗17m

" summary

OpenShift moves core components into 40+ operators and reports concrete lessons: build an start small MVP that first installs the app, then watches for config changes, then upgrades and backups; expose only app‑specific fields instead of the full podTemplate to hide Kubernetes complexity; avoid assuming custom node types or storage classes exist and rely on cluster defaults, letting admins supply restrictions; and separate admin and machine config so controllers never fight over the same fields.

AI-written summary · about

" chapters (7)

1. 0:00Start
2. 0:34deploy and manage your application on kubernetes
3. 5:11install your application on kubernetes
4. 7:47migrating over from our historical cluster topology to the new
5. 8:26rely on the clusters
6. 11:43define all the storage classes
7. 13:11separate the parts of the configuration

" related talks

• 20mLessons Learned Using the Operator Pattern to Build a Kubernetes PlatformPavlos Ratis · SREcon21
• 32mMinimalist Best Practices in Kubernetes OperatorsJonathan Berkhahn · Open Source Summit Europe 2023
• 43mLessons learned writing 10+ Kubernetes OperatorsLars Francke, Jannik Heyl · Berlin Buzzwords 2024
• 36mLessons learned writing 10+ Kubernetes Operators - Lars Francke and Jannik HeylLars Francke, Jannik Heyl · ContainerDays 2023
• 32mMinimalist Best Practices in Kubernetes OperatorsJonathan Berkhahn · CloudOpen @ Open Source Summit Europe 2023
• 36mEssential Patterns For Designing And Implementing Your OperatorMichael Hrivnak, Austin Macdonald · KubeCon + CloudNativeCon North America 2022
• 39mKubernetes Operators: Managing Complex Software with SoftwareJosh Wood, Jesus Carrillo · CloudNativeCon + KubeCon Europe 2017
• 45mHyper-Automate your Cloud Native JourneyMo Haghighi · Devnexus 2023