Project Setup Guide

This document provides comprehensive step-by-step instructions to deploy Infosys Agentic Foundry in Azure Kubernetes Cluster(AKS).

Prerequisites

Before setting up the project, ensure you have the following requirements and access permissions:

Ensure users have access to below:

Python 3.12+ - Required Python version
React - Frontend framework
Infosys Github Repo: Infosys-Agentic-Foundry
Ensure users must have their Azure OpenAI Keys and Endpoints, Speech to text Key and Endpoint.
Ensure Azure resources are created, and you have access/connectivity to push and pull from these resources
- Azure Container Registry (ACR)
- Azure Kubernetes Service (AKS)
- Azure Postgres Service (Compute size: Standard_B2s (2 vCores, 4 GiB memory, 1280 max iops), Storage: 32 GiB)
- Azure Linux Virtual Machine
Install Docker, Azure CLI, kubectl in your Azure VM
Create a namespace in the AKS cluster as per your requirement (Optional)

kubectl create namespace <namespace>

Azure Deployment

ARIZE PHOENIX

STEPS FOR DEPLOYING ARIZE PHOENIX IN AKS

Create a yaml file for deploying arize phoenix as a container, you can use the arize phoenix image in the yaml file.

nano filename1.yaml

Info

You can get the image from Docker - Phoenix or any other trusted source which your organization allows

Now you need to use this command for creating deployment and service:
```
kubectl apply -f filename1.yaml
```
You can check the pods deployed using the command below
```
kubectl get pods -n namespace
```
You can check the services deployed using the command below
```
kubectl get svc -n namespace
```
Note down the load balancer IP for the container. You need to update it in the .env of your backend and frontend folders before creating the respective docker images.

REDIS

STEPS FOR DEPLOYING REDIS IN AKS

Create a yaml file for deploying Redis as a container, you can use the redis image in the yaml file.

nano filename2.yaml

Info

You can get the image from Image Layer Details - redis:8.2.1 or any other trusted sources which your organization allows

Now you need to use this command for creating deployment and service:
```
kubectl apply -f filename2.yaml
```
You can check the pods deployed using the command below
```
kubectl get pods -n namespace
```
You can check the services deployed using the command below
```
kubectl get svc -n namespace
```
Note down the load balancer IP for the container. You need to update it in the .env of your backend folder before creating the respective docker image.

GRAFANA

STEPS FOR DEPLOYING GRAFANA IN AKS

Create a yaml file for deploying Grafana as a container, you can use the grafana image in the yaml file.

nano filename3.yaml

Info

You can get the image from Image Layer Details - grafana/grafana:11.2.0 or any other trusted sources which your organization allows

Now you need to use this command for creating deployment and service:
```
kubectl apply -f filename3.yaml
```
You can check the pods deployed using the command below
```
kubectl get pods -n namespace
```
You can check the services deployed using the command below
```
kubectl get svc -n namespace
```
Note down the load balancer IP for the container. You need to update it in the .env of your backend and frontend folders before creating the respective docker images.

ELASTIC SEARCH

STEPS FOR DEPLOYING ELASTIC SEARCH IN AKS

Create a yaml file for deploying elastic search as a container, you can use the elastic search image in the yaml file.

nano filename4.yaml

Info

You can get the image from elasticsearch - Official Image | Docker Hub or any other trusted sources which your organization allows

Now you need to use this command for creating deployment and service:
```
kubectl apply -f filename4.yaml
```
You can check the pods deployed using the command below
```
kubectl get pods -n namespace
```
You can check the services deployed using the command below
```
kubectl get svc -n namespace
```
Note down the load balancer IP for the container and update it in the OpenTelemetry YAML script.

OPEN-TELEMETRY

STEPS FOR DEPLOYING OPEN-TELEMETRY IN AKS

Create a yaml file for deploying OpenTelemetry as a container, you can use the OpenTelemetry directly in the yaml file.

nano filename5.yaml

Info

You can get the image from otel/OpenTelemetry-collector-contrib - Docker Image or any other trusted sources your organization allows

Now you need to use this command for creating deployment and service:
```
kubectl apply -f filename5.yaml
```
You can check the pods deployed using the command below
```
kubectl get pods -n namespace
```
You can check the services deployed using the command below
```
kubectl get svc -n namespace
```
Note down the load balancer IP for the container. You need to update it in the .env of your backend folder before creating the respective docker image.

MODEL SERVER

STEPS TO SETUP MODEL SERVER

For detailed instructions on deploying and configuring your model server, refer to the Model Server Deployment guide.

Note

You need to update the URL for the model server in the .env of the backend folder

BACKEND

STEPS TO SETUP BACKEND

Download Backend code from GitHub. For detailed instructions, see Download the Backend Project Code.

Login in to Azure VM
Download Backend source code folder into Azure VM
Before starting backend image creation make sure that arize phoenix, OpenTelemetry, Grafana, Elastic Search, Redis and Model server are setup as per instructions provided above. Update the respective urls of all these services in .env file.
Update the remaining values for the variables in the .env file.
Change working directory to the Backend Folder:
```
cd `<BE foldername>`
```
Create Dockerfile inside Backend folder to create docker image for Backend code.

Create backend image:

    docker build -f `<dockerfile-name>` -t `<tag-name>`

Retag the created image to ACR name:

docker tag localhost/<imagename>:<tag> <acr login server>/<imagename>:<tag>

Login to az and then login to acr:
```
docker login <acr login servername>
```

Push the retagged image to ACR:

docker push <acr login servername>/<imagename>:<tag>

Create backend deployment file:
```
nano <deployment filename.yaml>
```
Login to Azure Kubernetes

Execute the deployment file:

kubectl apply -f <deployment filename.yaml>

Check if the pods is deployed successfully:
```
kubectl get pods -n <namespace>
```
Check if the service is up & running successfully:
```
kubectl get svc -n <namespace>
```

FRONTEND

STEPS TO SETUP FRONTEND

Download Frontend code from GitHub. For detailed instructions, see Download the Frontend Project Code.

Login in to Azure VM
Download Frontend source code folder into Azure VM
Before starting frontend image creation make sure that arize phoenix, Grafana are setup as per instructions provided above. Update the respective urls of all these services in .env file.
Change working directory to the Frontend Folder:
```
    cd <Frontend foldername>
```
Create Dockerfile inside Frontend folder to create docker image from Frontend code.
In .env file of Frontend, update below service loadbalancer urls which were generated after deployment of backend server in Azure Kubernetes.
- REACT_APP_BASE_URL (use Backend url),
- REACT_APP_MKDOCS_BASE_URL (use mkdocs url),
- REACT_APP_LIVE_TRACKING_URL (use Arize phoenix url),
- REACT_APP_GRAFANA_DASHBOARD_URL (use Grafana url)

Create Frontend image:

    docker build -f <dockerfile-name> -t <tag-name>

Retag the created image to ACR name:

docker tag localhost/<imagename>:<tag> <acr login server>/<imagename>:<tag>

Login to az and then login to acr:
```
docker login <acr login servername>
```

Push the retagged image to ACR:

docker push <acr login servername>/<imagename>:<tag>

Create Frontend deployment file:
```
nano <deployment filename.yaml>
```
Login to Azure Kubernetes

Execute the deployment file:

kubectl apply -f <deployment filename.yaml>

Check if the pods is deployed successfully:
```
kubectl get pods -n <namespace>
```
Check if the service is up & running successfully:
```
kubectl get svc -n <namespace>
```

Troubleshooting

Virtual Environment Activation Fails

Permissions Error: Try running command prompt as administrator

Dependency Installation Errors

Update pip to the latest version:

python -m pip install --upgrade pip

Server or UI Not Starting

Verify the virtual environment is active
Check for typos in commands or file names
Ensure all dependencies are properly installed

To troubleshoot check pod logs in Kubernetes, By using below commands:

kubectl describe pods <pod_name> -n <namespace>
kubectl logs <pod_name> -n <namespace>