Kubernetes Native

  No new proprietary interface


Flexibility to choose platform elements


Platform workflows as Kubernetes YAMLs

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 their application workflows declaratively.

Platform-as-Code eBook

Kubernetes API extensions (Operators)

Kubernetes Operator, Kubernetes CRD

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 with Operator implementations for softwares like databases, queues, loggers, etc. Kubernetes API extensions or Operators form foundation for Platform-as-Code experience. 

Platform-as-Code process

Platform-as-Code refers to the process that application developers follow to create declarative platform workflows in Kubernetes YAMLs leveraging Custom APIs / Resources introduced by Operators along with built-in Resources. This involves discovering relevant information about the Custom Resources and binding the required Resources to define a workflow. 

Evolution of as-Code systems
Kubernetes Operators

- DevOps engineer is responsible for assembling the platform layer by selecting required Kubernetes CRDs/Operators. 

- Application developer then creates application platform workflows in Kubernetes YAMLs using various Custom and built-in Resources leveraging the platform layer. 

KubePlus approach to Platform-as-Code

Consistency across CRDs/Operators

We have created detailed guidelines to enable consistency and standardization across various community CRDs/Operators for enabling Platform-as-Code experience. 

Tooling for discovery and binding of APIs

 We have developed KubePlus API add-on to simplify discovery and use of Kubernetes Custom Resources towards building Platform-as-Code workflows. 


KubePlus API add-on

KubePlus API add-on is designed to provide discovery & binding of Custom Resources to orchestrate a technology stack in Kubernetes YAMLs. 

Discovery of Custom Resources :   

New endpoints to learn static and dynamic information about Custom Resources

Binding of Custom Resources :

New functional constructs to be used in YAML definition to bind Custom Resources

Existing technologies like Helm offer binding and resolution based on statically defined values. However there is a need for run-time resolution of dependencies in creating platform stacks. And KubePlus API add-on is designed to fill this gap without introducing any new CLI. 


Platform-as-Code Stakeholders

Extensions Developer


Comprehensive guidelines for Operator readiness for multi-Operator environments. 

DevOps Engineer


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

Application Developer


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

How Kubernetes API Extensions enable Platform-as-Code Experience

Learn more

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

Learn more

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

Learn more

Leverage full power of Kubernetes with KubeGarage.