Kubernetes
Jiandu includes reviewed Kubernetes examples for operators who already run a cluster. Kubernetes is not the shortest evaluation path: you are responsible for ingress, secrets, persistent storage, scheduling, and database recovery.
The manifests currently require authorized source-repository access. An anonymous 404 from the
clone URL means the examples are unavailable; no public image or manifest package is published.
Start by reading the manifests and their README together:
git clone https://github.com/zhyuri/jiandu.git
cd jiandu
ls examples/kubernetes
Before applying anything, decide:
- Which HTTPS ingress or sidecar will terminate TLS.
- Which stable public origin users will open.
- Which private address or network identifies the trusted proxy.
- Where the database and document blobs will persist.
- How secrets are injected without entering the image or repository.
- How you will run and test backup/restore jobs.
Jiandu still follows a single-process topology. Do not scale the application to multiple replicas against the same installation. Use your platform's rollout strategy to stop the old process before the replacement takes ownership.
See reverse proxy and HTTPS, database, and backup and restore before adapting the example.