Skip to content

Deployment Automation (Helm)

Deployment approach

Deployments are managed via Helm charts to provide: - reproducible configuration, - environment-specific overrides, - safe rollbacks.

Helm responsibilities

  • define Kubernetes resources,
  • inject configuration and secrets,
  • manage service dependencies.

Deployment flow

  1. CI decrypts required secrets (SOPS).
  2. Helm renders manifests with environment values.
  3. Kubernetes applies the release.
  4. Health checks verify readiness.

Rollback strategy

  • Helm maintains versioned releases; rollback is performed manually via helm rollback.
  • Model rollbacks are performed manually by updating the MLflow champion alias.
  • Data rollbacks are performed manually via dvc checkout.

Rollbacks are not triggered automatically. See Release & Rollback Policy for the full rollback process.

Safety guarantees

  • readiness probes gate traffic,
  • failed deployments do not receive traffic,
  • rollbacks do not require rebuilding images.