Current limitations

Review these boundaries before production rollout.

Product boundaries

• Volume-level SnapMirror only; no SVM-DR.
• No failover, break, resync, or reverse-resync workflow.
• No supported public JSON API beyond the authenticated who-am-I endpoint.
• Aggregates, policies, and schedules are discovered and selected by a person; DonkeyFleet does not create or automatically choose them.
• Operational ONTAP state is read through when needed rather than mirrored into a local cache.

Deferred capabilities

• A full importer that reconstructs every database record from destination intent markers is not available. PostgreSQL backups remain essential.
• DonkeyFleet protects the backing ONTAP volumes; it does not create, modify, or restore Kubernetes PV/PVC objects. Automated PV/PVC metadata enrichment is not available.
• Template-based destination naming is refused by provisioning. Use suffix or same_as_source.
• The minimum ONTAP version is not yet a stable product contract.
• Custom metrics currently cover four capacity gauges; use logs, notifications, and audit history for detailed reconcile and action outcomes.

Deployment constraints

• The bundled PostgreSQL chart is single-replica and intended for evaluation. Use an external, backed-up PostgreSQL service for production and crash recovery.
• Multiple DonkeyFleet replicas improve web availability, but reconciliation remains single-writer through a PostgreSQL advisory lock. Configure one shared OIDC session-encryption key across pods.
• The chart can render an Ingress or HTTPRoute but does not install an ingress controller, Gateway, NetworkPolicy, Vault, OIDC provider, External Secrets Operator, or managed database.

Configuration cautions

The tiering selector currently defaults to none while the accepted design default is all. Select the intended tiering policy explicitly.