Last week, Red Hat launched OperatorHub.io in collaboration with Microsoft, Google Cloud, and Amazon Web Services, as a “public registry” for finding services backed by the Kubernetes Operator.
According to the RedHat blog, the Operator pattern automates infrastructure and application management tasks using Kubernetes as the automation engine. Developers have shown a growing interest in Operators owing to features like accessing automation advantages of public cloud, enable the portability of the services across Kubernetes environments, and much more. RedHat also comments that the number of Operators available has increased but it is challenging for developers and Kubernetes administrators to find available Operators that meet their quality standards. To solve this challenge, they have come up with OperatorHub.io.
Features of OperatorHub.io
- OperatorHub.io is a common registry to “publish and find available Operators”.
- This is a curation of Operator-backed services for a base level of documentation. It also includes active communities or vendor-backing to show maintenance commitments, basic testing, and packaging for optimized life-cycle management on Kubernetes.
- The platform will enable the creation of more Operators as well as an improvement to existing Operators.
- This is a centralized repository that helps users and the community to organize around Operators.
- Operators can be successfully listed on OperatorHub.io only when then show cluster lifecycle features and packaging that can be maintained through the Operator Framework’s Operator Lifecycle Management, along with acceptable documentation for intended users.
Operators that are currently listed in OperatorHub.io include Amazon Web Services Operator, Couchbase Autonomous Operator, CrunchyData’s PostgreSQL, MongoDB Enterprise Operator and many more.
This news has been accepted by the Kubernetes community with much enthusiasm.
Operators are a key complementary piece to container orchestration for running distributed systems at scale, by incorporating domain specific knowledge for operating application workloads, especially when complex/stateful https://t.co/xbaXiEGaLU
— Marius Bogoevici (@mariusbogoevici) February 28, 2019
Great job @RedHat team with https://t.co/J3GKJkSPXX very excited to have the AWS Service Operator on there and findable by @kubernetesio users! 🤩🚀 Looking forward to seeing the operator ecosystem expand!
— Chris Hein (@christopherhein) February 28, 2019
This is not the first time that RedHat has tried to build on the momentum for the Kubernetes Operators. According to TheNewStack, last year, the company acquired CoreOS last year and went on to release Operator Framework, an open source toolkit that “provides an SDK, lifecycle management, metering, and monitoring capabilities to support Operators”.
Read Next
RedHat shares what to expect from next week’s first-ever DNSSEC root key rollover
RedHat shares what to expect from next week’s first-ever DNSSEC root key rollover