• Define your workflow
• Choose Kubernetes API extensions
• Build your Platform-as-Code YAMLs
• Required API Extensions (Operator)
• Platform-as-Code YAMLs
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.
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 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.
KubePlus does not introduce any new CLI. Teams use kubectl and Kubernetes YAMLs to create platforms as Code.
Our Operator guidelines and validation ensure one platform experience with uniform discovery, documentation and support across multiple extensions.
Kubernetes extensions embed platform specific workflows as Kubernetes objects and eliminate out-of-band custom automation.
This is a monthly subscription service which comes with KubePlus advisory support that helps you expedite building your purpose-built platform stack.
This is a yearly support subscription that can be used with your purpose-built platform stack on any public or private Kubernetes cluster.
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).
Simplify creation of micro-PaaSes or micro-services architectures on Kubernetes for running enterprise internal workloads.
Examples: AI/Analytics workloads, CI/CD
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.