Design archive — not shipped
This page describes a future or historical network, API, P2P, or deployment surface. The current product is a local alpha; there is no working network transfer, hosted server, public API/SDK, or deployable service.
Design Archive
Kubernetes Deployment Design Boundary
Historical manifests are not a supported cluster deployment.
Design, not a shipped service
The current product is a local alpha CLI and library. There is no hosted Dits service, complete repository remote, public API or SDK, managed webhook system, official server image, or supported production deployment. The items below are conditional design targets, not setup instructions or commitments.
Status
The repository contains historical Helm and Kubernetes research targeting backend images and services that are not part of the active workspace. There is no supported chart, operator, container image set, upgrade path, or production-grade Dits control plane.
Possible design targets
- A minimal chart generated from a real server's measured state, networking, and resource needs.
- Explicit persistent-volume, scheduling, disruption, scaling, and multi-zone behavior.
- Safe schema migrations, rollbacks, key rotation, observability, and recovery drills.
Prerequisites before implementation claims
- Published server images and a supported deployment architecture.
- Chart validation against maintained Kubernetes versions with upgrade and failure tests.
- Operational ownership, security policy, capacity evidence, and documented support scope.
What can be evaluated today
- Do not apply the historical manifests to a production cluster.
- Use Kubernetes-native storage and backup tooling independently of Dits if evaluating local artifacts in a disposable job.
- Treat any cluster experiment as user-owned infrastructure without Dits service support.