Fixed issue in langfuse deployment using Kubernetes

[nuwangeek]

This pull request makes several important improvements to the RAG Module’s infrastructure and deployment configuration. The main changes include standardizing the naming of the PostgreSQL database service across all Docker Compose files, updating database connection references, initializing the Langfuse database automatically, and introducing new Kubernetes configuration files for Helm chart management and container registry setup. These updates enhance consistency, reliability, and ease of deployment in both local and Kubernetes environments.

Docker Compose & Database Configuration Updates

• Standardized the database service name from rag_search_db to rag-search-db in all Docker Compose files (docker-compose.yml, docker-compose-test.yml, docker-compose-ec2.yml). This includes updating all references, container names, dependency conditions, and connection strings to use the new naming convention. [1] [2] [3] [4] [5] [6]
• Updated all environment variables and connection strings to reference rag-search-db instead of rag_search_db, ensuring consistency and preventing misconfigurations. [1] [2] [3] [4] [5]
• Modified volume mounts to include automatic initialization of the Langfuse database by mounting the init-langfuse.sql file and executing it if the database does not exist. [1] [2] [3]

Kubernetes & Helm Chart Enhancements

• Added a new Helm umbrella chart configuration in kubernetes/Chart.yaml to manage dependencies for all RAG Module components, improving modularity and deployment in Kubernetes environments.
• Introduced a container registry setup guide (kubernetes/CONTAINER_REGISTRY_SETUP.md) to document the process for building and pushing container images, supporting easier onboarding and deployment.

Environment Variable Adjustments

• Updated env.example to use the new database naming convention and connection string, reflecting the changes in Docker Compose and supporting seamless environment setup.

These changes collectively improve the reliability and maintainability of the deployment process for both local and Kubernetes environments, making it easier to manage and scale the RAG Module infrastructure.