Akan Kubernetes deployment is built around one app container, a Service, an Ingress, and persistent storage for sqlite data.
Deployment runs the app image.
Service exposes the app inside the cluster.
Ingress connects domains to the Service.
PVC keeps sqlite data across pod restarts.
Architecture
Think of the chart as four connected pieces. Users enter through Ingress, the Service routes traffic to the Pod, and the Pod stores local data through a PVC.
Mental model
Values
Use values to tune each environment. Debug can stay small, while main usually gets more CPU, memory, storage, and replicas.
values.yaml
Scale
`app.replica` becomes `AKAN_REPLICA` inside the pod. Use it with CPU and memory values to scale work safely.
`1,0,0`: small service with one request child.
`2,1,0`: more request capacity plus one batch worker.
`0,0,1`: one all-purpose child for simple environments.
Tips
Start with conservative requests and watch metrics before raising limits.
Resize sqlite storage before it becomes urgent.
Keep domain and subRoute values explicit so Ingress rules stay predictable.
