Add Helm chart for control plane deployment

[depadeto]

Context

Currently the control plane services are deployed via raw K8s manifests in manifests/gateway/control-plane-services.yaml. A Helm chart would make deployment configurable and easier.

Task

Create a Helm chart under charts/detoserve/ that packages:

• Smart Router
• Function Manager
• Tenant Manager
• Config Store
• Deployment Manager
• SkyPilot Bridge
• Redis

With configurable values for:

• Image tags
• Replica counts
• Resource limits
• Redis connection
• Environment variables

Reference

• manifests/gateway/control-plane-services.yaml — existing manifests
• docker-compose.yaml — service configuration

[fahrimert]

Hey! I've just opened a PR to address this issue: #10

I've packaged all the control plane services (Smart Router, Function Manager, Tenant Manager, Config Store, Deployment Manager, SkyPilot Bridge, and Redis) into a Helm chart under charts/detoserve/. Everything is fully configurable via values.yaml (image tags, replicas, resources, env vars, etc.) as requested.

Just a quick heads-up regarding the testing: I deployed and tested the chart on my local K3s cluster. Both helm lint and helm template pass perfectly, and the Kubernetes API successfully accepts all the generated manifests. However, since the control plane images are built locally via docker-compose and aren't currently hosted on a public container registry, the pods naturally fall into an ErrImagePull state.

Despite the missing public images, the Helm templating, service discovery, and deployment logic are fully wired up and working correctly.

Let me know what you think or if you need any adjustments to the values.yaml structure!