Chapter 11: Case Study for Core Operator – Etcd Operator
In the previous chapter (as for most of this book), we discussed Operators as a tool for managing applications that are deployed on Kubernetes. For most use cases, this is the main purpose of an Operator. In other words, the Operator serves to automate the applications that are developed by an organization. These applications are the products offered to users, and automating them helps to ship them without any issues and keep users happy. Beyond that, Kubernetes itself is simply the underlying architecture. As a part of this, it's usually assumed that Kubernetes doesn't need any additional automation as would be provided by Operators. After all, it was a key point of the early chapters in this book that Operators are not functionally much different than the native suite of controllers that make up the Kubernetes control plane in the first place.
However, there are situations where an Operator can be used to...