Helm chart setup

[drshika]

Helm Chart for UIUC.chat

This PR creates a helm chart and common setup configurations for UIUC.chat in Helm.

Testing

# Start Minikube with ingress addon
minikube start
minikube addons enable ingress

# Deploy the application
cd helm-chart
make dev NAMESPACE=uiuc

# Get access URL
minikube service uiuc-chat-frontend -n uiuc --url

see more detailed docs: LOCAL_K8S_TESTING.md

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
20717558	Triggered	Generic Database Assignment	da601a3	helm-chart/values-prod.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[drshika]

all the backend related things are still broken as pydub needs to be re-added to requirements.txt. this is while testing on macos.

[drshika]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
🛠 Guidelines to remediate hardcoded secrets
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

this can be ignored as the secrets are the defaults that people can re-set later

[drshika]

updated setup instructions:

Local Setup Instructions

Prerequisites

• Docker Desktop (or Docker Engine)
• kubectl (v1.24+)
• kind

Setup Steps

1. Create kind cluster:

   kind create cluster --config kind-config.yaml

2. Install NGINX Ingress:

   kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/main/deploy/static/provider/kind/deploy.yaml
   kubectl -n ingress-nginx wait --for=condition=Available --timeout=180s deploy/ingress-nginx-controller

3. Add hosts entry:

   echo "127.0.0.1 chat.local" | sudo tee -a /etc/hosts

4. Create TLS certs:

   openssl req -x509 -nodes -newkey rsa:2048 \
     -keyout chat.local-key.pem -out chat.local.pem -days 825 \
     -subj "/CN=chat.local" -addext "subjectAltName=DNS:chat.local"
   kubectl -n uiuc-chat create namespace uiuc-chat || true
   kubectl -n uiuc-chat create secret tls uiuc-chat-tls \
     --cert=chat.local.pem --key=chat.local-key.pem

5. Build and load images:

   # Frontend
   ./scripts/build-frontend-for-k8s.sh
   kind load docker-image uiuc-chat-frontend:latest --name uiuc-chat
   
   # Backend
   docker build -t uiuc-chat-backend:latest -f uiuc-chat-backend/Self-Hosted-Dockerfile uiuc-chat-backend/
   kind load docker-image uiuc-chat-backend:latest --name uiuc-chat

6. Deploy manifests:

   kubectl apply -n uiuc-chat -f k8s-app/backend.yaml
   kubectl apply -n uiuc-chat -f k8s-app/frontend.yaml
   kubectl apply -n uiuc-chat -f k8s-app/ingress.yaml
   kubectl -n uiuc-chat rollout status deploy/uiuc-chat-backend --timeout=180s
   kubectl -n uiuc-chat rollout status deploy/uiuc-chat-frontend --timeout=180s

7. Access the app:

   • Frontend: https://chat.local/
   • Keycloak: https://chat.local/auth/

For more details, see LOCAL_K8S_TESTING.md.

[drshika]

issues i'm facing right now:

• headers are not being passed between frontend next, keycloak and backend
  POST /api/UIUC-api/createProject returns 500