Deploy AKKO on OVHcloud MKS¶
OVHcloud MKS is the supported path for OVH-hosted production deployments.
AKKO also runs on plain OVH VMs with K3s — see
helm/examples/values-ovh.yaml in that case.
Prerequisites¶
| Requirement | Version |
|---|---|
| OVHcloud MKS | 1.30+ (3 nodes, B2-15 flavor minimum) |
| StorageClass | csi-cinder-high-speed (default, RWO) |
| Ingress | nginx-ingress (OVH add-on) or Traefik |
| Helm | ≥ 3.14 |
| DNS | public domain pointing to the OVH LoadBalancer |
One-command install¶
AKKO_DOMAIN=akko.customer.example \
AKKO_VERSION=2026.04 \
AKKO_VALUES_EXTRA=helm/examples/values-ovhcloud.yaml \
bash deploy-from-harbor.sh
values-ovhcloud.yaml pins:
global.storageClass: csi-cinder-high-speed(RWO)- LoadBalancer type for ingress-nginx with OVH-specific
service.beta.kubernetes.io/ovh-*annotations akko-docsPVC → RWO with init-container copy- VictoriaMetrics + logs layer enabled (ADR-020 Apache 2.0 stack)
- directory service disabled (GPL v3)
OVHcloud-specific notes¶
Storage¶
OVHcloud MKS ships csi-cinder-high-speed (RWO, SSD-backed). RWX requires
the optional ovh-managed-nfs addon — not required by AKKO 2026.04
(all PVCs are RWO).
LoadBalancer¶
OVH LoadBalancers are billed per-hour. Expect the first provisioning to take 2–3 minutes. Annotations already baked in the overlay :
Private registry (optional)¶
OVH offers a managed OVHcloud Container Registry compatible with the
Docker Registry API. To mirror AKKO images:
for img in cockpit postgres spark notebook trino ai-service mlflow \
airflow dbt mcp-trino mcp-openmetadata docs aden \
catalog-manager; do
skopeo copy \
docker://harbor.akko-ai.com/akko/akko-${img}:2026.04 \
docker://<your-ovhcloud-registry>/akko/akko-${img}:2026.04
done
Then override global.image.registry: <your-ovhcloud-registry>.
EU data residency¶
OVHcloud MKS runs in regions under French / EU jurisdiction (GRA, SBG, RBX, DE1). Combined with AKKO's sovereign stack (no telemetry outside your cluster, local LLMs via Ollama, all AGPL components replaced by Apache 2.0), this delivers a data-residency guarantee suitable for regulated industries. AKKO does not call any third-party API at runtime.
Verify installation¶
kubectl -n akko get pods
kubectl -n akko get ingress
kubectl -n akko exec svc/akko-trino -c trino -- trino --execute "SHOW CATALOGS"
Troubleshooting¶
| Symptom | Cause | Fix |
|---|---|---|
LoadBalancer stuck <pending> |
Cluster has zero public IP quota | Open ticket to OVHcloud support |
PVC Pending with ReadWriteMany error |
Overlay not applied | Make sure -f values-ovhcloud.yaml is passed |
| Pods CrashLoopBackOff on ARM nodes | OVHcloud offers some ARM SKUs; AKKO images are multi-arch for the most part, but check image manifests | docker manifest inspect harbor.akko-ai.com/akko/akko-<svc>:2026.04 |
TLS x509: certificate signed by unknown authority |
cert-manager Let's Encrypt not ready | kubectl describe certificate -n akko |