If you were using the Service Broker or some OpenShift Templates in OpenShift 3.11 in order to run a specific service such as MongoDB, PostgreSQL, etc. You might want to move to the specific operators for such technologies.
For example, if your application uses a MongoDB database, it will be very easy to use the MongoDB Operator in order to deploy and manage the MongoDB instance. The operator will take care of the MongoDB instance lifecycle helping you to focus on your application.
OpenShift 4 console features an operator marketplace called OperatorHub, you will find it under Operators -> OperatorHub
.
You can use OperatorHub within the OpenShift Console in order to search and install operators. You will be able to manage the installed operators using this same UI.
You might have some applications created by internal teams that are currently being deployed manually or using other methods that do not support managing the full lifecycle of the application. On top of that the operations team might need to ensure those applications are up and running.
In such cases, creating an operator to manage the full lifecycle of your application can be very beneficial, you will have the operational knowledge coded inside the operator. That way your operation teams can focus on more interesting tasks since the operational knowledge will be coded inside the operator.
The Operator SDK is a framework that uses the controller-runtime library to make writing operators easier by providing:
Operator can be written using Go, Ansible or even leveraging existing Helm charts.
You can learn more about how to create your own operators in the Building Operators on OpenShift interactive scenarios.
You can continue learning about operators in the following resources: