OperatorCon
Online Sessions

Challenges in Building a Multi-Cloud-Provider Platform With Managed Kubernetes

Building a cloud-agnostic platform used to be a challenging task as one had to deal with a large number of different cloud APIs and service offerings. Today, as most Cloud providers are offering a managed Kubernetes solution (e.g., GKE, AKS, or EKS), it seems like developers could simply build a platform based on Kubernetes and be cloud-agnostic. While this assumption is mostly correct, there are still a number of differences and pitfalls when deploying across those managed Kubernetes solutions.

This talk discusses the experiences made while building the ArangoDB Managed Service offering across and GKE, AKS, or EKS.

While the (managed) Kubernetes API being a great abstraction from the actual cloud provider, a number of challenges remain including for example networking, autoscaler, cluster provisioning, or node sizing. This talk provides an overview of those challenges and also discuss how they were solved as part the ArangoDB managed Service.

KubeCarrier - Automated multi cluster service management

One of Kubernetes greatest – and most difficult to keep – promises is the ability to eliminate much of the operational burden of managing applications and services on multi-cloud infrastructure.

Kubernetes Operators deliver on this promise by automating the management of applications’ and services’ lifecycle. However, provisioning, reconfiguring, and tearing down applications and services across multiple clusters, clouds and regions is still hard and time-intensive.

This talk will demonstrate how we automate the full lifecycle management of applications and services to end-users with a self-service catalog, independent of cloud, data center, and region.

Infrastructure Automation Operators

By Ken Owens, Mastercard

Infrastructure teams are siloed and even within the silos there are further silos. With the evolution of infrastructure as code and IaaS services, orchestration and automation of infrastructure services is segmented and often isolated. Early on, we determined to look at the orchestration and management of a deployment as a set of custom resources that need to be orchestrated to deliver a set of services. This presentation will describe the service catalog we developed as a set of CRDs. We will present the architecture we leveraged to accomplish this pattern: front-end (how infrastructure is consumed) and Back-end (how infrastructure is provisioned).

Introduction to KUDO - Kubernetes Operators The Easy Way

Kubernetes Operators are the next phase of the journey towards automating complex applications in containers. The Kudo project introduces an easy way to build Kubernetes operators using declarative YAML. Many Operators that exist today handle initial deployment, but they don’t provide automation for tasks like binary upgrades, configuration updates, and failure recovery. Implementing a production-grade controller for a complex workload typically requires thousands of lines of code and many months of development. As a result, the quality of operators that are available today varies. The Kudo project provides a universal operator to enable automated creation of operators for Kubernetes, in most cases just using YAML. In this talk, I’ll introduce the Kudo project, and demo the creation of a Kubernetes operator using Kudo.