This guide provides an introduction to Kubernetes Operator as a customer Kubernetes controller that allows you to deploy the Digital.ai Docker image on various platforms.
Operator is an application that monitors a custom Kubernetes resource and enhances its functionality to manage complex application instances. Kubernetes Operators work as extensions to Kubernetes application that help in packaging, deploying, and managing a Kubernetes application on behalf of the Kubernetes user. A Kubernetes Operator follows the basic Kubernetes and controller concepts, but uses the application-specific knowledge to automate the management of the complete life cycle of an application.
Managing application deployments with native Kubernetes objects can be difficult when handling complex applications with changing requirements. Kubernetes operators help in simplifying complex deployments by automating tasks that otherwise requires manual intervention or some form of automation.
The following are the key features of a Kubernetes Operator:
- Repeatable installation and upgrade methods on Kubernetes platforms
- Performs health checks of all the system components
- Records and redistributes the knowledge of field engineers to the Kubernetes users
Helm Charts are packaging formats that automates and simplifies deployment and management of Digital.ai Release on a Kubernetes cluster. They also provide some additional features necessary for the functioning of your container clusters. Kubernetes operators include complex configuration data within their packages in addition to packaging applications. Helm Charts is useful when your requirement is to automate the deployment with the default configuration settings. However, Kubernetes Operators provide custom configurations with your regular deployment.
Operator is an application that monitors the resource and interacts with Kubernetes API to create (or update) deployment with the specified number of pod replicas. An operator transforms the applications you deploy into intelligent Kubernetes objects, which contains the domain-specific schema. The controller is encoded with the operational intelligence or domain-specific knowledge to maintain the desired state of the object. Operators combine customer resource definitions (CRD) and custom controllers to eliminate the need for manual intervention when performing tasks like upgrade, failure recovery handling, and when scaling complex stateful applications.