Operators are usually written in Go by software developers that are highly familiar with Kubernetes.
Ansible® is a first class citizen in the Operator SDK. Ansible-based Operators provide a lower barrier to entry, faster iterations, and the power of Ansible and its ecosystem. Put more simply, an Operator is designed to watch and respond to the resources in your cluster to enable your application to run as desired. After the Operator SDK is invoked, it’s Ansible code as opposed to a common approach of handling these events with Go code.
Ansible Fits naturally into a Kubernetes Environment. Both use YAML to describe the desired state of the world. Both Ansible and OpenShift have vibrant communities working to solve common problems. Combining Ansible and Kubernetes frees up application engineers to minimize the new skill sets required to maximize time to delivery.
The same tried and trusted Ansible tooling lets you Automate and Orchestrate your applications across both new and existing platforms allowing teams to transition without having to learn new skills. With the k8s module, an Ansible user can manage applications on Kubernetes, on existing IT or across both with one simple language.
Using Ansible frees up application engineers, maximizes time to automate and orchestrate your applications, doing it across new and existing platforms with one simple language.
Senior Product Manager, Red Hat
This 30 minute interactive learning course from Katacoda provides a step-by-step example for developing an Ansible Operator using Operator SDK.
OperatorHub.io is a home for the Kubernetes community to share Operators. Find an existing Operator or list your own today.
The Red Hat Ansible Automation and Red Hat OpenShift teams have been collaborating to build a new way to package, deploy, and maintain Kubernetes native applications: Ansible Operator.
In this post I will show you how to use Roles published to Ansible Galaxy as an Operator to manage an application in Kubernetes.