Private cloud provider for Otomi Container Platform

Next to our providers for the most popular public cloud providers like AWS, Azure, and Google Cloud Platform, we have now added a new provider for running the Otomi Container Platform on Kubernetes in a private cloud, called the on-prem provider.

Creating an Office Lab Setup

To test the Otomi on-prem provider, we have set up a Kubernetes cluster on bare metal consisting of 3 nodes, each with 32GB memory, an Intel Xeon 3.6 GHz 8 core CPU, and 512GB SSD storage. For the host OS, we use SuSE Kubic. Why SuSE Kubic? Well because SuSE Kubic:

  • is a super modern and minimalistic OS with transactional updates
  • uses the CRI-O Container Engine 
  • is really simple to install and adding hosts can be easily automated
  • is tweaked for running container workloads
 For the storage layer, we use, which is based on CephFS. ensures that we can connect the PVCs to every node, and it also ensures redundancy. Encryption of PVCs is possible, but we have not yet investigated this.
With a central router for the on-prem Kubernetes cluster, all the endpoints are made available using MetalLB, and services use port forwarding to make them publicly accessible. For external-DNS and cert-manager we use Google DNS, but all other DNS solutions can be used as long as they are supported by cert-manager and external-DNS.

Enabling Hybrid and Multi-Cloud Scenarios

With the new on-prem provided added to the Otomi Container Platform, we can now support both hybrid and multi-cloud scenarios. This makes it possible to use a single pane of glass (Otomi Console) to deploy and manage container-based workloads on any Kubernetes cluster running the Otomi Container Platform, be it in the public cloud, in a private cloud, or in a hybrid setup.

All otomi Container Platform providers

Next Steps

With the new Otomi Container Platform on-prem provider and our experiences with the lab setup using Suse Kubic, we are now working on a new proposition: Otomi Appliance. With Otomi Appliance, you can get a complete and ready-to-use container platform as a hardware solution. We think Otomi Appliance would be particularly useful for event streaming and other “heavy” database and analytical applications. Stay tuned for more updates.

Share this article

Share on twitter
Share on reddit
Share on linkedin
Share on email
Share on facebook

Other Articles You Might Find Interesting


Otomi, looking back and ahead


Developer self-service for Kubernetes with Otomi

Discover the upsides and downsides of building your own Kubernetes-based container platform

Deep dive into the strategic risks IT Leaders will face in 6 to 12 months after deciding to build their own Kubernetes-based container platform solution.