Frequently Asked Questions

We understand that you might have some questions about Otomi. That's why we created a list with the most frequently asked questions:

To get started with Otomi, go to and install Otomi on your Kubernetes cluster using the Helm Chart (easy) or Otomi CLI (advanced).

Yes. Using a DNS zone is optional.

Yes. By default, Otomi is configured to use Keycloak as an IdP. Using Azure Active Directory as IdP for SSO and map groups to roles in Otomi is optional.

Yes. You can use the Otomi onprem provider to install Otomi on Kubernetes running on your own hardware, including Minikube. See here for more information and hardware requirements. Note that Otomi does not support ARM CPU architecture.

We understand that solutions like Rancher and OpenShift all propagate that their solutions come with integrated tools, but we take the term integrated a little more seriously. Within Otomi, integrated means that the application is pre-configured with Otomi base configuration values, the application has been adjusted to comply with all Otomi security policies, and that the application has been made user-aware and multi-tenant. An example: After installing Otomi, you can log in and go to Harbor. You don’t need to login into Harbor, Harbor already knows who you are and what you are allowed to do. Create a Team in Otomi, and Otomi will create a project in Harbor for the team and add a pull secret in the namespace of the team. Team members can log in and directly use the project in Harbor.

We can imagine when looking at the list of all pre-configured and ready-to-use apps, you might get the impression that Otomi is some kind of apps catalog. But the opposite is true. When you install Otomi, you will get all of these apps and they’re all already configured for you. Take for instance Istio. Otomi comes with an advanced ingress architecture using Istio. You can create a Team in Otomi and then a Service. Otomi in this case creates and configures all the Istio resources (gateway and virtual services). But this is only one example

Yes. Red Kubes provides an onboarding service. Contact us for more information and pricing. You can also reach out to one of our consulting partners

We provide multiple levels of support for issues related to Otomi features. See our services page for more information.

Do you still have questions? Please send a mail to and we'll answer them.

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.