For the complete documentation index, see llms.txt. This page is also available as Markdown.

Oobeya Installation Tutorial (Helm)

This guide explains how to install Oobeya on your Kubernetes cluster with Helm.

To install using the Helm Artifact Repository, you can follow the steps on ArtifactoryHub.

Contents

Warning: If you are not using Custom MongoDB, a StorageClass and a PVC are required.

Minimum Hardware Requirements:

  • 16GB RAM (Server requires at least 16GB of RAM to run efficiently for enterprises.)

  • 8 CPU / 4 Core

  • 100GB Disk Space

Supported External NoSQL Databases

  • MongoDB Atlas, Azure CosmosDB, AWS DocumentDB, GCP Firestore, Custom MongoDB Server.

Install Oobeya Helm Chart

Please create a namespace for Oobeya.

Please request a token from the Oobeya team for registry access.

To install using the Helm Artifact Repository, you can follow the steps on ArtifactoryHub.

You can download the chart package.

You can push the Oobeya directory to the ArgoCD or Kustomize Git Repository.

Configure Persistent Volumes

Persistent Volume Claim (PVCs) are defined in the following files:

Edit file to set the correct StorageClass name for your environment.

Configure custom MongoDB without PVC

If you enable External MongoDB, you will no longer need a Storage Class or a PVC.

Steps required to create a user and database for Oobeya:

If you're connecting to your external MongoDB, you'll need to fill in the blanks here:

Configuration

To access Oobeya from the browser, you need to add the domain name or machine IP to the configuration.

  • Please edit this:

  1. values.yaml.oobeyaDashboard

  1. values.yaml.oobeyaGateway

If you're using Nginx Ingress for access:

If you're using Traefik Ingress, similar definitions are included in the values.yaml file.

Installing Oobeya with Helm

If you want to deploy a specific version:

Last updated