Getting started with Kubernetes is a daunting endeavor, but a necessary one. For most organizations, it’s about digital transformation in the marketplace, where digital products and services are becoming the norm. Meaning, getting and maintaining an edge is highly dependent on your ability to deliver more features more quickly, and at an ever-increasing level of quality to stay ahead of your competition. In order to deliver great software quickly, Kubernetes is often touted as the solution.
Kubernetes Never Comes Alone
Choosing the More Valuable Engineering Work Creates Technical Debt
All this work on the container platform itself has zero value to an organization: it is simply something that must be done before more valuable work, like developing software, can be done. From a company perspective, it makes sense to try and minimize the amount of work spent on operating the platform; and this is often what happens under pressure by a product owner or manager: they don’t have the budget for it or don’t understand or appreciate the work that goes into it.

The technical debt is most visible in the ‘Glue’ between the products and services that make up the platform. In the custom integrations between, for instance, the container platform and the identity provider, or between the storage management solution and the container platform. These cracks in the glue start to form at each missed opportunity for maintenance, increasing the entropy over time and increasing the cracks each time a short-cut or easy-way-out is taken, forcing additional rework every time a change is needed as part of feature development work.
Gluing Kubernetes
As mentioned, the technical debt of the integrations between the different products in the container platform tends to have the biggest impact on the resilience and inertia, causing outages or forcing re-work to fix issues. So, it stands to reason that in order to remove this technical debt, we need a solution for keeping cracks from forming in the glue.

We need to Glue the Glue
In other words: standardize and automate not just Kubernetes, but all of the pieces in the container platform. Much like how organizations use a SaaS or managed service for Kubernetes to solve the complexity in Kubernetes, standardizing and automating the glue and integration between all products in the container platform solves the technical debt and complexity of the entire container platform.
Getting Started with Otomi is The Easy Way
Otomi Container Platform is a true turn-key solution, requiring zero initial investment. Pricing is pay-as-go-you and flexible, based on the number of container clusters under management.