Book Image

The Kubernetes Operator Framework Book

By : Michael Dame
1 (1)
Book Image

The Kubernetes Operator Framework Book

1 (1)
By: Michael Dame

Overview of this book

From incomplete collections of knowledge and varying design approaches to technical knowledge barriers, Kubernetes users face various challenges when developing their own operators. Knowing how to write, deploy, and pack operators makes cluster management automation much easier – and that's what this book is here to teach you. Beginning with operators and Operator Framework fundamentals, the book delves into how the different components of Operator Framework (such as the Operator SDK, Operator Lifecycle Manager, and OperatorHub.io) are used to build operators. You’ll learn how to write a basic operator, interact with a Kubernetes cluster in code, and distribute that operator to users. As you advance, you’ll be able to develop a sample operator in the Go programming language using Operator SDK tools before running it locally with Operator Lifecycle Manager, and also learn how to package an operator bundle for distribution. The book covers best practices as well as sample applications and case studies based on real-world operators to help you implement the concepts you’ve learned. By the end of this Kubernetes book, you’ll be able to build and add application-specific operational logic to a Kubernetes cluster, making it easier to automate complex applications and augment the platform.
Table of Contents (16 chapters)
1
Part 1: Essentials of Operators and the Operator Framework
4
Part 2: Designing and Developing an Operator
9
Part 3: Deploying and Distributing Operators for Public Use

Summary

This chapter concluded the primary development and publication of an Operator. If you have been following along up until this point while developing your own Operator, then congratulations! Your Operator is now published and accessible to new users thanks to the reach of OperatorHub. Starting from the early chapters of this book, we have shown the steps to design an Operator, develop its basic and advanced functionality with Go, build and deploy it for local testing, and finally, package and publish it for public distribution. However, very few Operator project life cycles will end at this point.

It is likely that most Operators will eventually need to evolve, change their provided features, and release new versions. Doing so in a consistent and predictable way benefits both your users and your maintainers by establishing expected release standards. These standards include policies for deprecation and timelines for new releases. In the next chapter, we will explain some...