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.
38 lines
839 B
Bash
Executable File
38 lines
839 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -e
|
|
|
|
source=$1
|
|
branch=$2
|
|
|
|
if [ -z "$source" ]; then
|
|
source="https://github.com/hanzoai/volume.git"
|
|
fi
|
|
|
|
if [ -z "$branch" ]; then
|
|
branch="master"
|
|
fi
|
|
|
|
docker build --build-arg="GIT_REPO=$source" --build-arg="GIT_BRANCH=$branch" -t lpp-distroless-provider:v0.0.1 -f Dockerfile.provisioner .
|
|
|
|
docker build -t lpp-distroless-helper:v0.0.1 -f Dockerfile.helper .
|
|
|
|
kind create cluster --config=kind.yaml --name test-lpp-distroless
|
|
|
|
kind load docker-image --name test-lpp-distroless lpp-distroless-provider:v0.0.1 lpp-distroless-provider:v0.0.1
|
|
|
|
kind load docker-image --name test-lpp-distroless lpp-distroless-helper:v0.0.1 lpp-distroless-helper:v0.0.1
|
|
|
|
kubectl apply -k .
|
|
|
|
echo "Waiting 30 seconds before deploy sts"
|
|
|
|
sleep 30
|
|
|
|
kubectl create -f sts.yaml
|
|
|
|
echo "Waiting 15 seconds before getting pv"
|
|
|
|
sleep 15
|
|
|
|
kubectl get pv |