Introducing OperatorHub.io, the new home for sharing Kubernetes operators
Having a hard time finding the right Kubernetes operators? Red Hat’s new OperatorHub.io is a public registry for Kubernetes Operator services. This curated list ensures developers can find exactly what they are looking for… without any documentation surprises.
Finding the right Kubernetes Operator can be a drag. Not only do you have to find something that works with your particular container setup, but you also have to double-check and make sure it was updated some time in the last 3 years. No one wants to spend a bunch of time implementing a solution, only to find out that it hasn’t got any documentation or a dead community.
That’s where Red Hat’s new OperatorHub.io comes in! OperatorHub.io is a public registry for Kubernetes operators, curated to make sure that there are no unpleasant surprises for developers. Now, developers can find the Kubernetes Operator-backed services their container implementations need!
What is OperatorHub.io?
Introduced in 2016, Operators are a way to automate infrastructure and app management tasks by using Kubernetes as the automation engine. Operators allow developers to utilize automation advantages like provisioning and scaling while still letting them maintain the portability of services with Kubernetes.
The Kubernetes community has really latched on to the idea of Operators and the number of open source Operators available has dramatically increased in the past three years. However, with any increase in supply, that means it can be a challenge to find the right one that fits a project’s need. Plus, there are quality issues at stake.
So, Red Hat put on their thinking cap and came up with OperatorHub.io. OperatorHub.io provides developers with a curated registry of Operator-backed services. What do they look for? Essentially, Red Hat wants to see a base level of documentation, active communities or vendor-backing to prove there are maintenance commitments, basic testing, and packaging for optimized life-cycle management on Kubernetes.
“The creation of OperatorHub.io provides a centralized repository that helps users and the community to organize around Operators,” said Aparna Sinha, a Group Product Manager at Google Cloud. “We look forward to seeing growth and adoption of OperatorHub.io as an extension of the Kubernetes community.”
Listing your operator on OperatorHub.io
The current list of operators is just a start! Although it already has big names like AWS Service Operator, Couchbase Operator, Jaeger Tracing, and MongoDB, they want to see more from the Kubernetes community!
To be listed, Red Hat explains that these Operators must successfully show cluster lifecycle features, packaging that can be maintained through the Operator Framework’s Operator Lifecycle Management, and acceptable documentation for its intended users.
Want your Operator listed? There’s a contribution guide here for more information. Every Operator listed on OperatorHub.io has to contain the Custom Resource Definitions (CRDs) as well as access control rules and references to the container image needed for installation and execution of your Operator.
First, test out the Operator on your own cluster. Then, you should submit a PR to the community registry with your YAML files. Right now, all the requests are being reviewed manually. Once it’s merged by the maintainers, your Operator will show up on OperatorHub.io for installation!
Basically, Red Hat is trying to lower the barrier for bringing new apps to Kubernetes. Hopefully, with OperatorHub.io, developers and organizations will be able to find the Operator-backed services they need and enjoy the flexibility of cloud services with Kubernetes.
Feel free to join in on the fun – there’s a community Kubernetes-Operator Slack Channel and the Operator Framework Google Group. Daniel Messer and Diane Mueller recorded a talk about “All Things Operators” at the OpenShift Commons Gathering that is also particularly helpful.