Sign-up for your free copy of Platform-as-Code eBook

Learn how Platform-as-Code approach enables teams to compose their platforms with Kubernetes API extensions and build application workflows declaratively.

Kubernetes extensibility and Platform-as-Code

Kubernetes Operators

One of the key reasons for Kubernetes’s popularity is its extensibility. Kubernetes API extensions (commonly referred as Operators) extend Kubernetes API to manage third-party software as native Kubernetes objects. There are 400+ GitHub repositories of Operators for softwares like databases, key-value stores, API gateways etc. 

Multi-Operator platform stacks

In order to build complex or stateful workflows like SaaS, CI/CD, AI, Analytics on Kubernetes, DevOps teams typically work with application developers to identify required platform elements like database, API gateway, SSL certificate manager etc. in 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. The challenges exist around securing the  multi-Operator stack and then being able to troubleshot Custom Resources efficiently.  


Platform-as-Code approach enables dynamic integration of disparate Kubernetes Operators and realization of codified platform workflows with focus on security and traceability.

Evolution of as-Code systems

CloudFormation, Terraform, Platform-as-Code, KubePlus

Any ‘as-Code’ system is designed to offer a common declarative language to provision a technology stack leveraging underlying APIs / resources. In the Kubernetes world, the set of control plane APIs in a Kubernetes cluster can be extended anytime by installing new Operators in a cluster. While the common language for building workflows using these APIs is Kubernetes YAML definition, the challenge is being able consume the Custom APIs introduced by the Operators efficiently. KubePlus API add-on is open-source tooling that helps with discovery and troubleshooting of Custom APIs. Platform-as-Code approach addresses the challenges in composing multi-Operator stacks and enables DevOps teams model, create, visualize and debug Kubernetes application workflows with Custom APIs. 

Platform-as-Code approach

Uniformity in Operators

We have created Operator maturity model and associated guidelines to enable consistency and standardization across various community CRDs/Operators.

Security profiling of the stack

We offer cluster level security profiling for multi-Operator stacks. This covers aspects like network and pod security, encryption at rest, audit settings etc. 

Tooling for traceability

 We have developed KubePlus API add-on to simplify modeling and troubleshooting Custom API/Resource based workflows. 

Kubernetes, KubePlus

KubePlus API add-on

KubePlus API add-on simplifies building workflow automation using Kubernetes Custom Resources with improved visibility and reliability. It brings uniformity in using variety of Custom APIs/Resources coming from different Kubernetes Operators or extensions. It allows users to discover and use Custom APIs/Resources more efficiently and visualize their dependencies with other APIs/Resources for debugging and monitoring purpose.

Extensions Developer


Comprehensive guidelines for Operator readiness for multi-Operator environments. 

Cluster Administrator


Extend Kubernetes without any custom automation using Curated Operators for Platform-as-Code. 

Platform Engineer


Repeatable and shareable way of creating platforms workflows as-Code with Kubernetes YAMLs.

Kubernetes and the future of as-Code Systems

How Kubernetes API Extensions enable Platform-as-Code Experience

Evolution of PaaSes to Platform-as-Code in Kubernetes world

Platform-as-Code: how it relates to Infrastructure-as-Code and what it enables