Manual AI/Run CodeMie Components Installation
Use this instruction to manually install AI/Run CodeMie by each component.
info
Manual steps are not mandatory when helm-charts.sh automated script was chosen.
Component Installation Order
This guide covers installation of the following components in order:
-
Storage and Ingress (if needed)
- Azure Storage Class
- Nginx Ingress Controller
-
- Elasticsearch
- Postgres-operator
- PostgreSQL
-
- Keycloak-operator
- Keycloak
- OAuth2 Proxy
-
- NATS
- NATS Auth Callout
-
- CodeMie API
- CodeMie UI
- MCP Connect
- Mermaid Server
-
- Fluent Bit
- Kibana
- Kibana Dashboards
Prerequisites Setup
Container Registry Access
Before deploying AI/Run CodeMie components, set up pull secrets:
-
Obtain
key.jsonfile from AI/Run CodeMie team -
Create the
codemienamespace:kubectl create namespace codemie -
Configure the secret. Replace
%%PROJECT_NAME%%with your project name:kubectl create secret docker-registry gcp-artifact-registry \
--docker-server=https://europe-west3-docker.pkg.dev \
--docker-email=gsa-%%PROJECT_NAME%%-to-gcr@or2-msq-epmd-edp-anthos-t1iylu.iam.gserviceaccount.com \
--docker-username=_json_key \
--docker-password="$(cat key.json)" \
-n codemie -
Reference the secret in deployments:
imagePullSecrets:
- name: gcp-artifact-registry
Container Registry Login
Login to AI/Run CodeMie container registry:
export GOOGLE_APPLICATION_CREDENTIALS=key.json
gcloud auth application-default print-access-token | helm registry login -u oauth2accesstoken --password-stdin https://europe-west3-docker.pkg.dev
Next Steps
Follow the installation guide in the order listed above, starting with Storage and Ingress.