Operators

Operators

  • Operators automate managing the entire lifecycle of distributed stateful applications deployed in the cluster. K8s cannot do this natively as it requires application specific knowledge to do so.
  • Operators are specific to the stateful application they manage. This is because different stateful applications like MySQL, ElasticSearch, etc. have different ways of setting up a distributed DB.
  • Operators use CRDs to extend the K8s API. So, we have operators for MySQL, Prometheus, Postgres, etc.
  • Operators monitor the stateful resources like a controller and makes the necessary changes if required.
  • Operator for a stateful application is built by experts in that application. The operator contains information like:
    • How to setup a multi-instance cluster?
    • How to run the cluster?
    • How to sync data between instances?
    • How to update the application instances?
  • Operators can be looked up on OperatorHub. These are built by the community.

Kubernetes Operator simply explained in 10 mins
Kubernetes Operator explained | What are Kubernetes Operators and how it works ► Prometheus Operator in practice: https://youtu.be/QoDqxm7ybLc 🚀 Learn what a Kubernetes Operator is, why this operator concept even emerged and why you should use Kubernetes Operators. To give you an overview, operators are used mainly for stateful applications. So I first compare how Kubernetes manages stateless and stateful applications. And then compare deploying and managing stateful applications without an operator compared to deploying it with a Kubernetes Operator. ► 1. StateLESS applications on Kubernetes 🚀 Kubernetes can manage the complete lifecycle of stateless applications in a fully automated way, because these applications don’t have business logic for deployment. So basically, once you deployed the application, you don’t have to sit there and control that your application is running properly. ► 2. StateFUL applications WITHOUT Operator 🤯 For stateful applications, like databases, the whole process isn’t as straightforward. They need more "hand-holding" during its whole lifecycle, because the replicas of stateful apps aren't identical. So, Kubernetes natively doesn’t have all the knowledge required 🤷🏻‍♂️ to automate the process of deploying every single stateful application. That’s why these kind of applications require manual intervention - people who "operate" these applications. ► 3. StateFUL applications WITH Operator 🦄 Operator solves this problem and basically replaces this "human" operator with a "software" operator. At its core it has the same control loop mechanism that Kubernetes has, that watches for changes in the application state. It also uses CRDs, which is basically a custom K8s component. So, it takes the basic Kubernetes resources and its controller concept as a foundation to build upon, and on top of that includes application-specific knowledge to automate the entire life cycle of the application it "operates". ▬▬▬▬▬▬ T I M E S T A M P S ⏰ ▬▬▬▬▬▬ 0:00 - Intro 0:45 - Stateless applications on Kubernetes 2:21 - Stateful applications WITHOUT Kubernetes Operator 4:52 - Stateful applications WITH Kubernetes Operator 7:47 - Summary 8:33 - Who creates these operators? ▬▬▬▬▬▬ Want to learn more? 🚀 ▬▬▬▬▬▬ Full Kubernetes and Docker tutorial ► https://bit.ly/2YGeRp9 DevOps Tools, like Terraform, Prometheus ► https://bit.ly/2W9UEq6 Complete K8s Application Setup ► https://youtu.be/EQNO_kM96Mo Jenkins Pipeline Tutorials ► https://bit.ly/2Wunx08 #kubernetes #kubernetestutorial #devops #techworldwithnana ▬▬▬▬▬▬ Connect with me 👋 ▬▬▬▬▬▬ Join private Facebook group ► https://bit.ly/32UVSZP Don't forget to subscribe ► https://bit.ly/3mO4jxT DEV ► https://bit.ly/3h2fqiO INSTAGRAM ► https://bit.ly/2F3LXYJ TWITTER ► https://bit.ly/3i54PUB LINKEDIN ► https://bit.ly/3hWOLVT ▬▬▬▬▬▬ Maybe interesting for you 😎 ▬▬▬▬▬▬ High-Quality and Hands-On Courses 👉🏼 https://bit.ly/3nIouPW Kubernetes 101 - cheatsheet for your work (handy ebook bundle) ► https://bit.ly/3mPIaiU Legal Notice: Kubernetes and the Kubernetes logo are trademarks or registered trademarks of The Linux Foundation in the United States and/or other countries. The Linux Foundation and other parties may also have trademark rights in other terms used herein. This video is not accredited, certified, affiliated with, nor endorsed by Kubernetes or The Linux Foundation.
Kubernetes Operator simply explained in 10 mins