mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-30 14:55:30 +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.
913 B
913 B
Contributing to Go
Go is an open source project.
It is the work of hundreds of contributors. We appreciate your help!
Filing issues
When filing an issue, make sure to answer these five questions:
- What version of Go are you using (
go version)? - What operating system and processor architecture are you using?
- What did you do?
- What did you expect to see?
- What did you see instead?
General questions should go to the golang-nuts mailing list instead of the issue tracker. The gophers there will answer or ask you to file an issue if you've tripped over a bug.
Contributing code
Please read the Contribution Guidelines before sending patches.
Unless otherwise noted, the Go source files are distributed under the BSD-style license found in the LICENSE file.