Extending Kubernetes with the Operator Framework at #OpenInfraSummit 2019 in Denver

https://www.openstack.org/summit/denver-2019/summit-schedule/events/23590/extending-kubernetes-with-the-operator-framework

Kubernetes scales and manages stateless applications quite easily - but handling complex, stateful workloads can often be a challenge. Databases, Distributed Caches, and file storage systems frequently include their own notions about clustering, which can turn dynamic management into a complicated and difficult excercize. Operators are Kubernetes agents that fulfill many common SRE tasks, such as how to deploy, scale, manage, backup, and even upgrade complex, stateful workloads.

This tutorial will provide an update on the Operator pattern, and a series of follow-along usage examples which demonstrate how to install and interact with these advanced, Kubernetes-aware solutions.

With an understanding of Operators in place, the session will go on to detail the Operator Framework and its main components, the Operator SDK and the Lifecycle management backplane.

Learn how to extend Kubernetes to support your own custom workload-management strategies and tactics using the Operator Framework!

What can I expect to learn?

The best advice on extending Kubernetes in a portable and cloud-native way.

This session provides architectural overviews, implementation patterns, and a look at a few popular solutions from this space. Learn how to establish higher-order interfaces that represent the logical domain expertise (and perhaps the ideal product output) of a Kubernetes SRE.

Transcript

1. Extending Kubernetes with the Operator Framework Ryan Jarvinen ryanj@redhat.com May 1, 2019 bit.ly/extendedinfra
2. Ryan Jarvinen Developer Advocate, Red Hat twitter/github: @ryanj
3. What is Kubernetes?
4. Part1: “Why should you care about Operators?”
5. Scaling stateless apps: easy
6. $ kubectl scale deploy/staticweb --replicas=3
7. scale up count=1 desired=3 Spec vs Status
8. start count=3 desired=3 Spec vs Status Spec vs Status
9. What about apps that store data?
10. Creating a database is easy
11. $ kubectl run db --image=quay.io/my/db
12. Running a database over time is harder
13. • Resize/Upgrade • Reconfigure • Backup • Healing
14. 1. Every application on any platform must be installed, configured, managed, and upgraded over time 2. Patching is critical to Security
15. 15 Anything not automated is slowing you down
16. If only Kubernetes knew...
19. Operators are automated software managers that deal with installation and lifecycle of Kubernetes applications
20. 1) Application-specific custom controllers 2) Custom resource definitions (CRD) Extending the Kubernetes API
21. Application-Specific Controllers
22. Custom Resource Definition (CRD) kind: ProductionReadyDatabase apiVersion: database.example.com/v1alpha1 metadata: name: my-production-ready-database spec: clusterSize: 3 readReplicas: 2 version: v4.0.1
23. { }
24. What is etcd? Example: etcd Operator • distributed key-value store • primary datastore of Kubernetes • stores and replicates all Kubernetes cluster state
25. Example: etcd Operator kind: EtcdCluster apiVersion: etcd.database.coreos.com/v1beta2 metadata: name: example-etcd-cluster spec: size: 3 version: "3.1.0"
26. Example: etcd Operator
28. learn.openshift.com/operatorframework Try It! Hands-On Operator Tutorials
29. github.com/operator-framework/awesome-operators • etcd • Prometheus • Elasticsearch • MySQL • “and many more!” Meet the Community!
30. https://github.com/operator-framework
34. Operator SDK
35. OpenShift V4 http://try.openshift.com
36. 36 https://github.com/operator-framework https://coreos.com/operators/ https://github.com/operator-framework/awesome-operators https://coreos.com/blog/introducing-operator-framework https://learn.openshift.com/operatorframework/ Resources
37. 37 Q & A
38. THANK YOU! twitter.com/RedHat linkedin.com/company/red-hat youtube.com/user/RedHatVideos twitter.com/ryanj openshift.com @RyanJ bit.ly/extendedinfra