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.
31 lines
916 B
Go
31 lines
916 B
Go
package reflect2
|
|
|
|
import (
|
|
"reflect"
|
|
"unsafe"
|
|
)
|
|
|
|
// DefaultTypeOfKind return the non aliased default type for the kind
|
|
func DefaultTypeOfKind(kind reflect.Kind) Type {
|
|
return kindTypes[kind]
|
|
}
|
|
|
|
var kindTypes = map[reflect.Kind]Type{
|
|
reflect.Bool: TypeOf(true),
|
|
reflect.Uint8: TypeOf(uint8(0)),
|
|
reflect.Int8: TypeOf(int8(0)),
|
|
reflect.Uint16: TypeOf(uint16(0)),
|
|
reflect.Int16: TypeOf(int16(0)),
|
|
reflect.Uint32: TypeOf(uint32(0)),
|
|
reflect.Int32: TypeOf(int32(0)),
|
|
reflect.Uint64: TypeOf(uint64(0)),
|
|
reflect.Int64: TypeOf(int64(0)),
|
|
reflect.Uint: TypeOf(uint(0)),
|
|
reflect.Int: TypeOf(int(0)),
|
|
reflect.Float32: TypeOf(float32(0)),
|
|
reflect.Float64: TypeOf(float64(0)),
|
|
reflect.Uintptr: TypeOf(uintptr(0)),
|
|
reflect.String: TypeOf(""),
|
|
reflect.UnsafePointer: TypeOf(unsafe.Pointer(nil)),
|
|
}
|