Kubernetes Deployment (Planned)
Planned Feature
Kubernetes/Helm chart support is planned but not yet available. This page outlines what to expect when the feature is released.
PACKAGE.broker will support deployment on Kubernetes using an official Helm chart for production-ready, scalable deployments.
Planned Features
Helm Chart
- Official Helm repository
- Production-ready defaults
- Configurable resource limits
- Support for PostgreSQL, Redis, S3-compatible storage
- Ingress configuration templates
- SMTP email configuration for user invitations
Deployment Options
- PostgreSQL: Production database backend
- Redis: Caching and session storage
- S3-compatible: Object storage for artifacts
- Horizontal scaling: Multiple pod replicas
- SMTP: Email configuration for user invitations and notifications
SMTP Configuration
The Helm chart will support SMTP configuration via values.yaml:
config:
smtp:
host: "smtp.gmail.com"
port: "587"
user: "your-email@gmail.com"
from: "noreply@example.com"
existingSecret: "smtp-credentials" # Use existing Kubernetes secret
passwordKey: "smtp-password" # Key in secret for password
Note: Store SMTP passwords in Kubernetes secrets, not directly in values.yaml. See the Helm chart values.yaml for the complete SMTP configuration structure.
Timeline
Target: Q1 2026
See Roadmap for detailed timeline and updates.
Current Deployment Options
While Kubernetes support is being developed, you can deploy PACKAGE.broker using:
- Docker Quickstart - Single container deployment
- Cloudflare Workers Quickstart - Serverless edge deployment
Getting Updates
- Check GitHub Issues for Kubernetes-related updates
- Follow GitHub Discussions for announcements
- Review Roadmap for feature status
Next Steps
- Deploy using Docker Quickstart or Cloudflare Workers Quickstart
- Review Architecture to understand deployment requirements
- Check Roadmap for Kubernetes implementation timeline
- See Deployment Overview for production considerations