Otomi is an open-source multi-cloud, multi-tenant container platform with SSO on top of Kubernetes. It has pre-configured settings and automation for common concerns such as DNS, certificates, ingress, networking, security, policies, scalability, and so on. It aims to deliver a mature turnkey platform for teams to deploy containerised workloads onto. Using Istio and Knative under the hood it comes pre-installed with industry-leading applications for telemetry, logging, image storage & scanning, CD (and yes, CI, if you don’t have that yet 😉 etc. The console’s UI takes an OS-like approach offering open source applications that are aware of the teams, its members, and their permissions. The philosophy is to focus on providing the necessary glue including sane defaults to make working with these apps a seamless experience. It takes a developer-first approach, uses familiar tooling, and promotes open-source software at its core. Instead of taking on technical debt by hiding open-source building blocks behind one catch-all frontend, it puts the individual applications in the spotlight they deserve. Its flexible and sustainable architecture allows scaling your applications as well as your workforce.

Sounds too good to be true? Then please join, because the truth lies in the details 😉 Afterward, we hope to get feedback on the choices made and are open to suggestions and discussion.

This webinar has 3 parts:

1) Architecture overview

2) DevOps workflow

3) Developer workflow

The first part will elaborate on the architecture and give you an overview of the design. 

The DevOps perspective will showcase the otomi cli and take you through the steps to:

Configure & validate values and deploy the platform onto a fresh cluster.

Configure a team service to expose their self deployed workload on a public URL behind the company SSO.

Configure and expose a service publicly for another team by deploying their container image, using Knative.

The last part will target the developer workflow, showing you how to modify and extend the functionality of Otomi-core. We will add a new core app resulting in the following:

A new app chart including the necessary wiring to expose a limited set of values.

Update the values schema so that these values can be validated.

Commit to build an image tag from the branch name, and configure a target cluster to use that tag.

Hope to see you join, and maybe even get involved!