CloudARK

Platform-as-Code

Save time & efforts in building your Kubernetes Platforms

Building Kubernetes Native platform layer

  • What all API extensions (Operators) do we need in our platform layer – MySQL, Backup, ElasticSearch, CertManager, Nginx..? 


  • How can developers learn about the API extensions (Operators) added to the cluster? How can they consume these new APIs to build their platform workflows? 


  • Is there any one-stop-shop to get solution engineering and enterprise support on these community extensions? 


image1

KubePlus - Kubernetes Native Technology Integration as-a-Service

Catalog of curated API extensions (Operators)

image2

 • Curated API extensions (Operators) based on comprehensive guidelines 

• Custom Resource (API) YAML templates

Platform-as-Code Practice to build your platform layer

image3

• Define your workflow

• Choose Kubernetes API extensions 

• Build your Platform-as-Code YAMLs

Your Purpose-built Platform distribution with support

image4

     • Required API Extensions (Operator)

     • Platform-as-Code YAMLs

     • API discovery add-on

 

Why Platform-as-Code at the core of KubePlus?

There are primarily two steps involved in building a Kubernetes Native platform layer as shown below: 

1. DevOps Engineer - Assembles required Kubernetes Operators (API extensions) to construct the platform layer.

2. Application Developer - Consumes newly added Custom Resources (APIs) in Kubernetes YAML definitions to realize a platform workflow.


At CloudARK, we look at this entire process of building and using Kubernetes Native platform layer from the end user’s perspective. Kubernetes YAMLs that an application developer defines are nothing but declarative representation of a platform workflow and hence can be termed as Platforms as-Code. ‘Platform-as-Code’ approach simplifies the experience of Kubernetes Native Platforms for application developers. 

image5

Platform-as-Code refers to the process that application developers follow to create declarative platform workflows in Kubernetes YAMLs leveraging Custom Resources and built-in Resources. 

Platform-as-Code Practice

Platform-as-Code practice offers advisory support on assembling right API extensions (Operators). We directly embed our Platform-as-Code expertise within your platform engineering team to build your platform layer. 

image6

KubePlus Purpose-built 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 specific workflows as Kubernetes objects and eliminate out-of-band custom automation. 

Interested in building your Kubernetes platforms with KubePlus?

image7

KubePlus Integration Service Subscription

  • Get your Kubernetes platform integrations up and running.
  • Engagement with the platform engineering and development teams leveraging our Platform-as-Code practice. 

This is a monthly subscription service which comes with KubePlus advisory support that helps you expedite building your purpose-built platform stack. 

KubePlus Purpose-built Platform Distribution

  • Ongoing enterprise support for your KubePlus Purpose-built Platform Stack built with our KubePlus integration service.

This is a yearly support subscription that can be used with your purpose-built platform stack on any public or private Kubernetes cluster.

To know more contact our sales

Use Cases

Kubernetes Multi-tenancy

SaaS workloads

Simplify creation of multi-tenant platform stacks for SaaS workloads running 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).   

image8

Enterprise internal workloads

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

Examples: AI/Analytics workloads, CI/CD 

image9

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.

Platform-as-Code at the core of KubePlus