Skip to main content

Overview

Otomi Console​

Otomi Console is the web UI of Otomi and offers access to all integrated apps and self-service tasks.

Otomi Console has a topbar showing a cluster and team selector, the logged-in user and a dark/light-mode. The team selector allows to switch to your desired context. Otomi Console also has a menu on the left. This menu shows the sections "Platform", "Team $name" and "Cluster".

Platform section​

The Platform section in the left menu provides access to:

  • Dashboard
  • Apps: All active and inactive apps. Activate apps by dragging them to the active apps section
  • Shortcuts: A list off all shortcuts created on this platform
  • Clusters: A list of all known Kubernetes clusters running Otomi
  • Policies: A list of all available security policies and their configuration for this platform
  • Teams: A list of all Teams using this platform
  • Builds: A list of all builds created on this platform
  • Secrets: A list of all secrets created on this platform
  • Workloads: A list of all workloads running on this platform
  • Services: A list of all services running on this platform
  • Settings: Specific configuration of the platform

Team section​

The Team $name section gives access to:

  • Apps: All the apps available to the team on this platform
  • Shortcuts: All shortcuts available to the team on this platform
  • Builds: A list of all builds created by the team
  • Secrets: A list of all secrets created by the team
  • Workloads: A list of all team workloads
  • Services: A list of all team services
  • Settings: Specific team configuration options

Cluster section​

The Cluster section shows:

  • Cluster information such as name, cloud, region, k8s version, otomi version, etc
  • A "Download KUBECFG" link to download a KUBECONFIG file that gives access to the namespace of the team selected. Admins can download one with cluster-admin permissions (giving access to all namespaces) by setting the team selector to '-'. You can use it like export KUBECONFIG=$file_location or by merging it with another KUBECONFIG file like .kube/config.
  • When Otomi uses an automatic generated CA or Let's Encrypt staging certificates, a "Download CA" link is provided.

Please visit the official Kubernetes documentation about managing kube contexts.