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 otomi.io and install Otomi on your Kubernetes cluster using the Helm Chart (easy) or Otomi CLI (advanced).
No. One of the prerequisites to use Otomi is a DNS zone. We understand that not everybody will have a DNS zone available. That is why we are now adding support for wildcard DNS services for IP addresses.
No. A prerequisite for Otomi is to use an Azure Active Directory as IDP for SSO and mapping groups to roles in Otomi. But we are already working on removing this dependency. Soon Otomi by default will use Keycloak (installed by Otomi) as an IDP.
Otomi is an enterprise-grade Kubernetes-based platform and comes with a complete suite of applications that have been configured to support the most common (enterprise) use cases. Although it is possible to turn some applications off (like Harbor, Kubeapps, Gatekeeper, Drone, and Vault), Otomi still consumes a serious amount of resources. We understand that some people would like to be able to test Otomi, without having to set up a complete K8s cluster with multiple worker nodes. That’s why we are thinking about creating a lightweight version of Otomi. Keep an eye out on our socials for future updates.
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