Building on the momentum for the Kubernetes Operators, Red Hat has set up a public registry, OperatorHub.io, designed to make it easier for developers and admins to find pre-tested Operators for their applications.
“The Operator hub is really designed to be the public registry for finding and sharing Kubernetes Operators and Operator-backed services,” said Diane Mueller, Red Hat director of community development.
Amazon Web Services, Google Cloud and Microsoft are also participating in the project — all three offer commercial Kubernetes services. A hub full of easily-accessible operators could make it much easier for their users to set up and deploy applications.
CoreOS introduced the Operator pattern in 2016 as a way to speed the deployment of applications onto a Kubernetes-based cluster. In essence, the operator format gives the software developer a template that will tell Kubernetes how to deploy and maintain an application, including detailed instructions on how to build and deploy that application. The operator, packaged as a stand-alone container, packages the configuration details into a YAML-defined custom resource definition (CRD) that Kubernetes can understand. An associated controller ensures that the resultant cluster is maintained by the operator specification.
Red Hat acquired CoreOS last year, and it has since continued to champion the role of Operators. The company has since released the Operator Framework, an open source toolkit that provides an SDK, lifecycle management, metering and monitoring capabilities to support Operators.
Beyond the initial use case of providing a packaging format to install the complex application onto the clusters, Operator are also used to simplify “day two ops,” Mueller said. “Everything beyond the initial install is what makes the Operators framework take off, and get such widespread awareness.”
Day-two operations can consist of duties like seamlessly upgrading an application, as well as patching, backups and overall lifecycle management.
Red Hat is soliciting the submission of Operators from third parties. Each Operator submitted will go through a series of basic operational tests. Moreover, the packaging must meet the criteria of the Operator Framework’s Operator Lifecycle Management.
Initially, the hub is expected to have about a dozen Operators, though the company expects that number to rapidly multiply once word gets out. Already in stock are Operators include the Couchbase Autonomous Operator, the etcd Operator, the Jaeger Operator for Kubernetes, the Kubernetes Federation Operator, the MongoDB Enterprise Operator, the Prometheus Operator, the Redis Operator, and the Strimzi Operator for Apache Kafka.
Those of you in California who want to get more information on Operators, check out the Kubernetes Operator Framework hands-on workshops, both at ScaleX in Pasadena on March 7 and at the OpenShift Commons Gathering on Operating at Scale in Santa Clara on March 11.
Excited to launch https://t.co/dDTp54Uhc5, a place to share high-quality Kubernetes Operators.
— Rob Szumski (@robszumski) February 28, 2019
Red Hat is a sponsor of The New Stack.
Feature image via Pixabay.