Fast vs. easy: Operators by the numbers
Working knowledge required / 30- minute breakout session
Log in and click on the ‘Watch & Learn’ tab to add this video breakout sessions to your agenda.
The Operator SDK supports 3 ways of implementing your app's operational knowledge: using Go, Helm, or Ansible. A compiled language like Go is usually faster than an interpreted language like Ansible and Python. But how much does it matter when implementing an Operator? How much speed is sacrificed for faster iterations and easier maintenance? We tried to answer these questions by benchmarking Operators written with the three Operator SDK types to manage the life cycle of a large number of application custom resources on a cluster. We then looked at ways to optimize execution speed of Ansible-enabled Operators to close the speed gaps with the other types of Operators. In this session, we’ll present our findings, lessons learned, and ways to optimize execution speed with development efficiency. You’ll see how to evaluate these tradeoffs for their own clusters.
Tim Appnel, Red Hat - is a product manager, evangelist and "Jack of all trades" on the Ansible team at Red Hat.
Fabian von Feilitzsch, Red Hat - is an author and software developer from St. Louis, MO. He has used Ansible since 2013.
James Cammerata
Jeff Geerling, Midwestern Mac, LLC - is an author and software developer from St. Louis, MO. He has used Ansible since 2013
Learn how to deploy a Redis cluster based on virtual machines powered by Red...
Learn how a platform engineering team streamlined the deployment of edge...
Learn how to use the OpenShift Virtualization Windows UEFI installer pipeline...
Learn how to customize a kube-burner workload to deploy virtual machines...