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.
28 lines
564 B
Bash
Executable File
28 lines
564 B
Bash
Executable File
#!/bin/bash
|
|
|
|
if [ -n "$(git status --porcelain --untracked-files=no)" ]; then
|
|
DIRTY="-dirty"
|
|
fi
|
|
|
|
COMMIT=$(git rev-parse --short HEAD)
|
|
GIT_TAG=${DRONE_TAG:-$(git tag -l --contains HEAD | head -n 1)}
|
|
|
|
if [[ -z "$DIRTY" && -n "$GIT_TAG" ]]; then
|
|
VERSION=$GIT_TAG
|
|
else
|
|
VERSION="${COMMIT}${DIRTY}"
|
|
fi
|
|
|
|
if [ -z "$ARCH" ]; then
|
|
ARCH=$(go env GOHOSTARCH 2>/dev/null || uname -m | sed -e 's/x86_64/amd64/' -e 's/aarch64/arm64/')
|
|
fi
|
|
|
|
SUFFIX="-${ARCH}"
|
|
|
|
TAG=${TAG:-${VERSION}${SUFFIX}}
|
|
REPO=${REPO:-hanzoai}
|
|
|
|
if echo $TAG | grep -q dirty; then
|
|
TAG=dev
|
|
fi
|