feat: DevContainer 2.0.0-dev with serverless architecture and unified Helm chart #52
Reference in New Issue
Block a user
Delete Branch "feature/serverless-2.0.0"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
This PR introduces DevContainer 2.0.0-dev with a complete serverless architecture and unified Helm chart supporting both persistent and dynamic deployment modes.
Issues Addressed
WEB_FILE_MANAGERDeployment Modes
Persistent (
deploymentMode: persistent) — DefaultTraditional v1.x behavior. Long-lived deployment with PVC storage, MCP sidecars, and SSH support. Fully backward compatible.
Dynamic (
deploymentMode: dynamic) — NewServerless model using Knative auto-scaling from 0 to N instances, with dynamic GitHub repository routing via URL path and Authentik authentication.
Architecture (Dynamic Mode)
Usage Examples
CI/CD
Both images are now built automatically on push to
feature/serverless-2.0.0:ghcr.io/cpfarhood/devcontainer2.0.0-devfeature/serverless-*ghcr.io/cpfarhood/devcontainer-routing-proxy2.0.0-devfeature/serverless-2.0.0The chart defaults to
image.tag: 2.0.0-devso Helm installs pull the development images automatically.Key Changes
Container Enhancements
WEB_FILE_MANAGER(#11)startapp.shHelm Chart (v2.0.0-dev)
deploymentModefield:persistent|dynamicknative-service.yaml,routing-proxy.yaml,dynamic-ingress.yamldynamic.*values section for Knative, routing proxy, ingress, and Authentik configvalues-dynamic.yamlexample for serverless deploymentsServerless Infrastructure
serverless/CI/CD Updates
feature/serverless-*branches2.0.0-devtags for both devcontainer and routing proxy imagesBackward Compatibility
All existing 1.x deployments continue working unchanged:
deploymentModedefaults topersistentTest Plan
helm templaterenders correctly for both modes2.0.0-devtag/github/{owner}/{repo}🤖 Generated with Claude Code