As Kubernetes evolves into the de facto leader on open source container orchestration, leaving behind incumbents like Mesosphere and Docker platform, it becomes more and more complicated to navigate through the myriad of projects, initiatives, and options. The image below can give you a sense of that complexity. You can find an interactive version on the CNCF website.
With so much complexity where do you start?
Beyond navigating the complexity of projects and initiatives, your organization should also consider:
• Vendor consolidation: It has started, and it´s expected to intensify in the coming year. So caution is advised when betting on a specific vendor software for the long run. Notably, IBM-Red Hat (OpenShift is definitely a driver for that operation, while IBM had already a base of Kubernetes for services like Watson and their IBM public cloud), VMware acquiring Heptio and launching their own version of Kubernetes (through Pivotal) earlier in the year, and NetApp acquiring StackPointCloud.
• Vendor differentiation has not happened yet: At the time of the writing of this post, the count is at 50 different distributions of Kubernetes, 31 certified Kubernetes hosted services, 72 Kubernetes Certified Service Providers, 23 different provisioning (automation and configuration) tools, 29 different storage solutions, etc. As the ecosystem evolves, we anticipate there will be leaders on each category, probably tied to specific industry use cases but considering Kubernetes is still in its infancy, that differentiation has not yet happened.
• Kubernetes is constructed in a very inclusive way: This has helped spark the generation and development of a massive ecosystem, not necessarily on the same open source software principles. The level of specialization of some of these components is key and makes Kubernetes a highly configurable component of your IT. Companies will end up having more than one type of Kubernetes, just as they have more than one type of application or service running on it.
And this is how we get to the point of this article, the importance of looking at Kubernetes as a toolkit to build a flexible infrastructure to be provisioned to your application or services demands, rather than forcing these services to accommodate into a single monolithic configuration of your clusters. Unlike cloud configuration, containerization allows and requires an application-driven approach.
What is Kubernetes Foundations Service?
Kubernetes Foundations Service from Rogue Wave OpenLogic bundles the delivery of a Kubernetes cluster built through full automation and configured from an application perspective: AI, Kafka, NodeJs, Java, Microservices, CI/CD environment, etc… It can be iterated for as many use cases as needed, and it includes:
• Fully-automated scripts to deploy your cluster on any substrate of your choice: VMware, OpenStack, baremetal, or any of the public clouds.
• Full monitoring, alerting, and log aggregation of your clusters based on Prometheus and Grafana, and extensible to your application layer.
• Upstream Kubernetes, guaranteeing no lock-in, no proprietary software unless specifically requested.
• Hands-on training on the technologies used in your service, from the application layer to the infrastructure components
• Unique consultative support extending break-fixing, granting direct access to our Enterprise Architects to consult on how to´s, best practices, and help development and operations teams navigate through the ecosystem complexity. Our support does not only cover the Kubernetes but also the docker, the underlying operating system and most importantly, the applications running on top.
Kubernetes Foundations can also be extended to include:
• Containerization and migration of your specific workloads including a comprehensive migration plan and executed through full automation and testing.
• CI/CD implementation of your development projects based on Jenkins.
• Real-time, end to end, data processing integration service built on Apache Kafka, Spark, and Cassandra.
• Extended monitoring and alerting to your use case or applications layer, based on Prometheus and Grafana OSS projects.