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.
17 lines
649 B
Plaintext
17 lines
649 B
Plaintext
Hanzo Volume
|
|
Copyright (c) 2014-present Hanzo AI, Inc.
|
|
|
|
This product includes software developed by Rancher Labs, Inc.
|
|
|
|
local-path-provisioner
|
|
https://github.com/rancher/local-path-provisioner
|
|
Copyright (c) 2018-2025 Rancher Labs, Inc.
|
|
Licensed under the Apache License, Version 2.0.
|
|
|
|
This work is a derivative of that project at tag v0.0.36. The provisioner's
|
|
behaviour is unchanged; what differs is the name it answers to and the paths an
|
|
operator reads. The Apache-2.0 licence it was published under is the licence
|
|
this carries, unaltered — see LICENSE.
|
|
|
|
Third-party dependencies are vendored under vendor/ and keep their own licences.
|