CloudARK

Platform-as-Code

Enabling Platform engineering teams Deliver More Value Faster.

Purpose-built Kubernetes Native Platforms

Kubernetes Native

  No new proprietary interface

Composable

Choose your platform software elements

Declarative

Platform workflows as-Code in 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 application workflows declaratively.

Platform-as-Code eBook

Present Alternatives for building Kubernetes Platforms

Pre-built Platforms

image1

Lack of flexibility and proprietary interfaces.

DIY Platforms

image2

  One-off automation and expensive to maintain.

Our Approach

Aggregating enterprise-ready Kubernetes API extensions

Purpose-built Kubernetes Native Platforms

image3

Kubernetes Native, Composable and Declarative platforms as-Code

Kubernetes Native Platforms

image4

One of the key reasons for Kubernetes's popularity is ability to extend its API set by adding required ‘Kubernetes API Extensions’ also known as ‘Custom Resource Definitions (CRDs)’ or 'Operators'.  There are 400+ GitHub repositories of Kubernetes Operators for variety of softwares such as API gateways, relational / non-relational databases, load balancers, application workloads like Spark, Tensorflow, etc. 

When it comes to building a Kubernetes Native platform layer, single CRD/Operator is not enough. Platform layer typically requires more than one platform elements such as database, load balancer, API gateway, caching / queuing engine etc. So a Kubernetes Native platform layer involves multiple Operators and associated Custom APIs / Resources. 

DevOps Engineer

What all API extensions / Operators do we need? 

Application Developer

How do we consume new APIs introduced by extensions? 

Manager

How do we get enterprise-ready extensions and their support? 

Customized training on Kubernetes extensibility and building Kubernetes Native platforms

Learn more

Core technology: Platform-as-Code

Platform-as-Code simplifies defining technology stacks for Kubernetes Native Platforms.

image5

The goal of an as-Code system for Kubernetes is to simplify the process of defining the technology stacks in Kubernetes YAMLs leveraging available Custom or built-in APIs.  KubePlus Purpose-built Platforms come with an API add-on for enabling Discovery and Binding of Kubernetes custom APIs/Resources for it.

More on Platform-as-Code

KubePlus Purpose-built Kubernetes Native Platforms

Accelerate building Kubernetes Native Platforms with KubePlus subscription.

image6
More on KubePlus

Guarantee of hybrid multi-cloud application portability

image7

Due to composable and declarative nature of Platform-as-Code approach, enterprises can easily create their platform stacks repeatably on any Kubernetes cluster. This simplifies transfer or recreation of workloads across hybrid and multi-cloud environments. It also enables the ability to lift & shift or burst workloads between private and public clouds. 

What are people saying?

"I like the idea of KubePlus reducing some of the complexity and bringing consistency where it is badly needed."

- Systems Analyst and Consultant

 "KubePlus can lower the complexity in creating end to end stateful applications ready for production."

- DevOps & CI/CD team leader

"New trend: Platform-as-Code, an evolution of IaaS and PaaS that decreases vendor lock-in by implementing and adopting cloud platform dependencies in declarative way. I think companies that will specialize in delivering on-premise solutions in this space will compete in the next decade."

- Facebook post by an Enterprise Architect

"KubePlus can give me the flexibitlity to manage lifecycle events  (like post-startup db validations, replica additions to mongodb replica sets, kafka custom rebalancing etc.) at the top-level rather than lower level of docker images."

- DevOps Engineer