replicatedhq / replicatedhq/platform-examples

feat(mlflow): add KOTS snapshot/backup configuration for stateful services

Open
#171 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go Template
Stars
9
Forks
6
No merged PRs in 30d

Description

Parent epic: #166
Integration branch: feat/mlflow-enterprise-patterns

Add KOTS snapshot configuration for PostgreSQL and MinIO PVCs with restore documentation.

Scope

  • Add backup configuration to release/kots-app.yaml: backup.volumes for PostgreSQL and MinIO PVCs
  • Add snapshot-related preflight collector to release/kots-preflight.yaml (Velero/snapshot provider check)
  • Create applications/mlflow/docs/backup-restore.md documenting:
    • How KOTS snapshots work with CloudnativePG and MinIO Tenant PVCs
    • Full backup procedure
    • Restore procedure with operator ordering considerations
    • Verification steps post-restore

Files touched

  • applications/mlflow/release/kots-app.yaml (add backup config)
  • applications/mlflow/release/kots-preflight.yaml (add snapshot check)
  • applications/mlflow/docs/backup-restore.md (new file)

PR target

Branch PRs to feat/mlflow-enterprise-patterns (not main).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading applications/mlflow/release/kots-app.yaml and applications/mlflow/release/kots-preflight.yaml, then review the existing MLflow deployment and operator ordering. Add the PostgreSQL and MinIO PVC snapshot configuration, the snapshot-provider preflight check, and applications/mlflow/docs/backup-restore.md. Done means the backup, restore, and post-restore verification procedures are documented and configuration targets the integration branch.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgresql
Domain
databases, documentation, infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.