No new proprietary interface
Choose your platform elements
Declarative platform definition
Learn how Platform-as-Code approach enables teams to compose their platforms with Kubernetes API extensions and build their application workflows declaratively.
Lack of flexibility in platform elements and proprietary interfaces.
Lack of uniformity and expensive to maintain platform stacks.
Kubernetes-native, Composable and Shareable platforms as-Code
One of the key reasons for Kubernetes popularity is ability to extend its API set by adding required ‘Kubernetes API Extensions’. ‘Custom Resource Definitions (CRDs)’ or 'Operator' are more common terms used to refer to 'Kubernetes API extensions'. CRDs/Operators add Custom Resources (new APIs) and associated Custom Controller to manage desired platform software natively on the cluster.
There are 400+ GitHub repositories of Kubernetes Operators for a variety of software such as API gateways, relational databases, non-relational databases, Backup/restore, SSL cert management, load balancers, application workloads like Spark, Tensorflow, etc. CRDs/Operators are Kubernetes Native by design as they seamlessly integrate with Kubernetes core functions such as kubectl CLI, Helm package manager, Audit logs 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. That means building a Kubernetes Native platform layer involves assembly of multiple Operators.
What all API extensions / Operators do we need?
How do we consume new APIs introduced by extensions?
How do we get enterprise-ready extensions and their support?
Platform-as-Code aims to simplify the process of building and consuming Kubernetes Native Platforms using community API extensions. It builds upon Kubernetes’s inherent declarative nature and leverages Kubernetes YAMLs to define end-to-end platform workflows. As a result, enterprises get a Kubernetes-native, composable and shareable way of building their platform workflows.
Due to composable and shareable 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.
"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