mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-01 00:48:00 +00:00
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.
27 lines
539 B
INI
27 lines
539 B
INI
# top-most EditorConfig file
|
|
root = true
|
|
|
|
# Unix-style newlines with a newline ending every file
|
|
[*]
|
|
end_of_line = lf
|
|
insert_final_newline = true
|
|
indent_style = space
|
|
indent_size = 2
|
|
trim_trailing_whitespace = true
|
|
|
|
# Set default charset
|
|
[*.{js,py,go,scala,rb,java,html,css,less,sass,md}]
|
|
charset = utf-8
|
|
|
|
# Tab indentation (no size specified)
|
|
[*.go]
|
|
indent_style = tab
|
|
|
|
[*.md]
|
|
trim_trailing_whitespace = false
|
|
|
|
# Matches the exact files either package.json or .travis.yml
|
|
[{package.json,.travis.yml}]
|
|
indent_style = space
|
|
indent_size = 2
|