-
Notifications
You must be signed in to change notification settings - Fork 0
feat: Add Production Infrastructure and Kubernetes Support #8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
r4770
wants to merge
14
commits into
main
Choose a base branch
from
k8s-ready
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Add health check routes (/api/health, /api/ready, /api/metrics) - Add Docker Compose for local development - Add Dockerfile.dev for development builds - Update email service with development mode - Fix middleware order for health endpoints - Update .gitignore and .dockerignore
- Add centralized logger with JSON output - Fix duplicate 404 logging issue - Clean error responses without stack traces - Add request logging middleware - Support LOG_LEVEL environment variable
- Add production-ready Helm chart with configurable options - Support internal PostgreSQL or external Azure Database - Include health checks, security contexts, and network policies - Add HPA with custom scaling behavior - Include pre-install migration job and post-install tests - Support multiple environments (dev/staging/prod) - Add ServiceMonitor for Prometheus integration
- Add comprehensive documentation with Mermaid diagrams - Document API workflows, database schema, and architecture - Include local development setup (containerized and non-containerized) - Add Fly.io deployment instructions - Document data format requirements with examples - Add monitoring, troubleshooting, and API usage examples
- Restore Dockerfile.app (production optimized multi-stage build) - Update GitHub Actions to use Dockerfile.app instead of Dockerfile
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎯 Overview
This PR adds production-ready infrastructure components to the DataViz service, including health checks, metrics, structured logging, and a complete Helm chart for Kubernetes deployment.
📋 Summary of Changes
🏥 Health & Monitoring Infrastructure
/api/health
,/api/ready
,/api/startup
for Kubernetes probes/api/metrics
(uptime, memory, database status, user/chart counts)🐳 Container & Orchestration
🛠️ Development Experience
🗂️ Key Files Added
Infrastructure Components
Kubernetes Deployment
🔧 Enhanced Features
Health Checks for Kubernetes
/api/health
- basic service health/api/ready
- database connectivity check/api/startup
- application initialization verificationProduction Monitoring
Multi-Environment Support
🚀 Local Testing
The Docker Compose setup allows testing all infrastructure components locally:
📊 Kubernetes Deployment
🛡️ Production Features
🔄 Backward Compatibility
All existing APIs and functionality remain unchanged. The additions are:
✅ Benefits
This PR enables production deployment while providing better local development tools for testing the new infrastructure components.