Building complex enterprise workflows on Kubernetes


  • What all API extensions (Operators) do we need  – MySQL, Cassandra, ElasticSearch, CertManager, Nginx..? 
  • How can developers build their platform workflows leveraging Custom APIs / Resources introduced by the Operators? 


Present alternatives

Kubernetes providers


Bundle of only the most common extensions.

DIY stacks


Significant in-house efforts. 

Our approach with KubePlus iPaaS

Purpose-built Kubernetes Platform Stacks

Kubernetes Platforms

Efficiently integrate disparate Kubernetes API extensions (Operators).

Powered by novel Platform-as-Code approach

Platform-as-Code enables teams to make their platform workflows repeatable by codifying them as YAML definitions leveraging Kubernetes Custom APIs / Resources.


Platform-as-Code tools and techniques 

- eBook on Platform-as-Code. 

- Comprehensive Operator curation guidelines

- KubePlus API add-on for use of Custom APIs. 

- Catalog of curated Operator Helm charts. 


Monthly Platform-as-Code subscription 

- Pre-built enterprise workflows of popular use cases. 

- Purpose-built workflows

  • Assessment and recommendation of Operators for your enterprise workflow. 
  • Solution engineering and curation of Operators.
  • Codifying your platform workflows in YAMLs. 

Co-create your platform stack with KubePlus Subscription

Kubernetes iPaaS

Sign up for KubePlus Monthly Subscription

Augment your Kubernetes expertise with our Platform-as-Code subscription by directly embedding our Platform-as-Code techniques within your platform engineering team. 

Your KubePlus Purpose-built Platform Stack

Kubernetes Platforms

Composed of Kubernetes Operators

A Kubernetes Operator is a Kubernetes API extension that adds Custom APIs to manage third party software like databases, key-value stores, etc. on Kubernetes. Your KubePlus Platform Stack is composed of enterprise-ready Kubernetes Operators that are required in your application workflows. 


Kubernetes Native interfaces

Platform-as-Code promotes use of Kubernetes Native interfaces like kubectl CLI and YAML definition. This enables teams to build their Kubernetes platform layers without having to learn any new interfaces. 

KubePlus Platform advantage

No new CLI

KubePlus does not introduce any new CLI. Teams use kubectl and Kubernetes YAMLs to create platforms as-Code. 

One platform experience

Our Operator guidelines and validation ensure one platform experience with uniform discovery, documentation and support across multiple extensions.

Eliminate ad-hoc scripts

Kubernetes extensions embed platform workflows as Kubernetes objects and eliminate out-of-band custom automation. 

Use cases

Kubernetes Multi-tenancy

SaaS workloads

Simplify running multi-tenant SaaS workloads on Kubernetes.

- Cloud-Native SaaS (offerings designed grounds-up for SaaS based delivery model).

- Cloud-Enabled SaaS (multi-tenant hosting of any classic install-anywhere type of software).   

Kubernetes workloads

Enterprise internal workloads

Simplify creation of micro-services architectures on Kubernetes for running enterprise internal workloads.

Examples: AI/Analytics workloads, CI/CD 

Kubernetes migration

Transformation to Cloud Native technologies

Accelerate cloud native technology adoption to support business transformation initiatives.

- Migrating legacy applications to cloud native architectures.

- Migrating containerized workloads from other orchestration engines to Kubernetes.

Why Platform-as-Code?

  In order to build complex or stateful workflows like AI, Analytics, CI/CD or SaaS applications on Kubernetes, DevOps teams typically work with application developers to identify required platform elements like database, API gateway, SSL certificate manager etc. for their stacks. Then a custom platform layer is constructed on base Kubernetes using API extensions (Operators) of these platform elements. Integration of these Operators and use of the Custom APIs/Resources introduced by them to realize the platform workflows is not easy. Platform-as-Code approach is designed to bring consistency and ease of use in such multi-Operator platform stacks. It enables efficient integration of disparate Kubernetes Operators and realization of codified platform workflows.


Platform-as-Code simplifies creating platform workflows with

  1. Consistency across various Operators.
  2. Tooling that helps with discovery and binding of Custom APIs/Resources.