There are some straightforward and declarative techniques to request Kubernetes to run your applications. Typically, YAML declarations or Helm charts are sufficient to define your applications. Especially simple applications that are stateless. But more complex applications that are stateful, have persistence or change over time need a more dynamic management style. The Operator pattern has emerged as the way to control applications that not only run but also scale, backup, restore, adapt, update, and manage their more complex features.

One fundamental nature of Kubernetes is its extensibility. By leveraging Custom Resource Definitions (CRDs) and extending the controllers, the Operator pattern was born.

In this session, you will see how this pattern emerged. We will explore how the architecture works natively on Kubernetes. We will see numerous open-source Operators available for you to apply. There are a variety of ways to develop Operators to meet your business requirements. We will unpack the choices and advantages of the different development technique. The session will conclude by exploring a series of examples on how to write your custom Operators.

Learn how to extend Kubernetes with Operators to support the solutions for your business needs.

Embrace, extend and embellish. That whole extinguish thing was so 90s.