LogoLogo
  • E.D.D.I Documentation
  • Getting started
  • Your first bot
    • Understanding your first bot
  • Bot Manager GUI
  • Creating your first Chatbots
    • Create a "Hello World" bot
    • Create a bot that reacts to user inputs
  • Import/Export a Chatbot
  • Managed Bots
  • Deployement management of Chatbots
  • Extensions
  • Behavior Rules
  • HttpCalls
  • Langchain
  • Output Configuration
  • Conversations
  • Passing context information
  • Output Templating
  • Semantic Parser
  • Git support
  • Docker
  • Setting Up EDDI on AWS with MongoDB Atlas
  • RedHat Openshift
  • Metrics
  • FAQs
Powered by GitBook
On this page
  • EDDI-operator
  • Usage

Was this helpful?

Export as PDF

RedHat Openshift

PreviousSetting Up EDDI on AWS with MongoDB AtlasNextMetrics

Last updated 4 years ago

Was this helpful?

E.D.D.I is enterprise certified to run on RedHat Openshift and is therefore offered with support on the redhat marketplace:

EDDI-operator

Usage

Openshift Setup

Prerequisites

  • Openshift 4.3+ Deployment

  • Block Storage (Preferable with storage class)

Installing the Operator from the RedHat Marketplace

  1. Head to the Operator section in the Admin Overview and go to the OperatorHub

  2. Choose which version of the EDDI Operator to use (Marketplace or normal)

  3. Click install and leave the defaults (All Namespaces, Update Channel alpha and Approval Strategy Automatic)

  4. Click subscribe

Using the operator

After the installation of the operator, go to the installed Operators menu point and click on the first EDDI menu on top and create a new Instance. Below is a minimal CustomResource. The storageclass_name has to be changed to the name of an existing StorageClass, the environment variable will be added as a label to the mongoDB deployment.

apiVersion: labs.ai/v1alpha1
kind: Eddi
metadata:
  name: eddi
spec:
  size: 1
  mongodb:
    environment: prod
    storageclass_name: managed-nfs-storage
    storage_size: 20G

The operator will create a route automatically so you can access the EDDI admin panel. Per default the route will take the name of the CR. With the CR from above the route would look like this: eddi-route-$NAMESPACE.apps.ocp.example.com ($NAMESPACE will be the name of the project where the CR was created.)

https://marketplace.redhat.com/en-us/products/labsai
Docker Repository on Quay