mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
zeekay
b61441f7d7
A fork of Rancher's local-path-provisioner at v0.0.36. The behaviour is unchanged and deliberately so — a directory on the node a pod lands on is the right thing for a disk. What changes is identity. The provisioner answers to hanzo.ai/volume rather than rancher.io/local-path. That is not branding: two provisioners sharing one name race for the same claims, and a stock k3s carries the upstream one, so a cluster running both would settle our storage by chance. Data lives at /var/lib/hanzo/volume, so reading a Hanzo cluster does not mean learning another vendor's directory. Apache-2.0 as published, unaltered, with Rancher's attribution in NOTICE. The README says what this is not: durability. A volume here dies with its node. That is hanzoai/replicate's question, one layer up, and keeping the two apart is what lets the disk stay this simple.
956 B
956 B
How to contribute
We definitely welcome patches and contribution to this project!
Tips
Commits must be formatted according to the Conventional Commits Specification.
Always try to include a test case! If it is not possible or not necessary, please explain why in the pull request description.
Releasing
Commits that would precipitate a SemVer change, as described in the Conventional
Commits Specification, will trigger release-please
to create a release candidate pull request. Once submitted, release-please
will create a release.
For tips on how to work with release-please, see its documentation.
Legal requirements
In order to protect both you and ourselves, you will need to sign the Contributor License Agreement.
You may have already signed it for other Google projects.