Writing a Kubernetes Operator: the Hard Parts - Sebastien Guilloux, Elastic

Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io
Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects
Writing a Kubernetes Operator: the Hard Parts - Sebastien Guilloux, Elastic
Building a custom controller or operator to manage your Kubernetes applications is becoming easier, with the help of libraries and tools such as controller-runtime and Kubebuilder. Putting together an initial working prototype is fairly straightforward, but devil is in the details. This talk focuses on lessons learned while writing Kubernetes controllers for stateful workloads with the help of controller-runtime. It covers some of the "hard parts". The operator lives in the past: how to deal with resources cache inconsistencies? Why does idempotency matter? What can you do when StatefulSets are not good enough for the orchestration you need? How to empower advanced users but still provide good defaults? What namespace(s) should the operator have access to? How to test that monster you ended up building? These are questions engineers at Elastic had to answer.
sched.co/UaeV

[@jack_brannan]

Thanks, why didn't I see this report a month ago??? I danced on almost all the rake described here and it is clear why there are so few such working and not demonstration operators...

[@KaneYork]

re: the section leading up to 24:00: I think a better way to describe that is, "the user is allowed to shoot themselves in the foot, but that's okay because they will know immediately & fix it".