Technology RadarTechnology Radar

Kubernetes Operators

devops
This item was not updated in last three versions of the Radar. Should it have appeared in one of the more recent editions, there is a good chance it remains pertinent. However, if the item dates back further, its relevance may have diminished and our current evaluation could vary. Regrettably, our capacity to consistently revisit items from past Radar editions is limited.
Trial

We've faded out Kubernetes Operators as a standalone recommendation because they are such a central part of Kubernetes that their use appears self-evident.

Trial

The Kubernetes Operators allow to manage application configuration within Kubernetes through custom resources. The operators are implemented as Kubernetes controllers and all interaction happens through the Kubernetes API. This allows to manage application deployment and configuration with the same toolset, it also allows to create another abstraction layer to describe the desired application state and let the operator decide how this state should be reached.

Kubernetes Operators are widely available for many community projects. These can be shared and found on operatorhub.io. Implementing custom operators is greatly simplified through the Operators SDK which is used as base for many existing implementations.

We use operators in most projects and prefer them to custom management code. We encourage teams to try the existing community operators for e.g. observability and operations tasks.