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

Working with the Kubernetes community

This chapter focused heavily on the standards, policies, and timelines of Kubernetes as they relate to Operator development. While it might seem that these are fixed, prescriptive decrees, the reality is that they are fluid frameworks for development created through an open and fair process. This process is organized by contributors from different companies all over the world, and it is always open to new voices.

As a developer for the Kubernetes platform, you have inherent stock in the community that organizes Kubernetes upstream. Therefore, improvements or concerns that affect you are likely to affect others as well. This is why it's not only OK but encouraged that you play an active role in upstream development alongside your own Operator. If nothing else, doing so serves to benefit your own development, as the open process allows you to help steer upstream work as you feel it should be done.

Getting involved is as simple as sending...