What all Kubernetes API extensions (Operators) do we need?
How do we use Custom APIs to define our platform workflows?
Is their any one-stop-shop to get support for our multi-Operator stack?
Bundle of only the most common APIs
Significant in-house efforts
Efficiently integrate disparate Kubernetes API extensions (Operators).
Platform-as-Code enables teams to make their platform workflows repeatable by codifying them as YAML definitions leveraging Kubernetes Custom APIs / Resources.
Monthly Platform-as-Code subscription
- Purpose-built multi-Operator stacks
Augment your Kubernetes expertise with our Platform-as-Code subscription by directly embedding our Platform-as-Code techniques within your platform engineering team.
A Kubernetes Operator is a Kubernetes API extension that adds Custom APIs to manage third party software like databases, key-value stores, etc. on Kubernetes. Your KubePlus Platform Stack is composed of enterprise-ready Kubernetes Operators that are required in your application workflows.
Platform-as-Code promotes use of Kubernetes Native interfaces like kubectl CLI and YAML definition. This enables teams to build their Kubernetes platform layers without having to learn any new interfaces.
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 workflows as Kubernetes objects and eliminate out-of-band custom automation.
Simplify running multi-tenant SaaS workloads 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-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.
In order to build complex or stateful workflows like AI, Analytics, CI/CD or SaaS applications on Kubernetes, DevOps teams typically work with application developers to identify required platform elements like database, API gateway, SSL certificate manager etc. for 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. Platform-as-Code approach is designed to bring consistency and ease of use in such multi-Operator platform stacks. It enables efficient integration of disparate Kubernetes Operators and realization of codified platform workflows.