mirror of
https://github.com/hanzoai/volume.git
synced 2026-10-30 14:55:30 +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.
57 lines
2.1 KiB
Go
57 lines
2.1 KiB
Go
/*
|
|
Copyright 2024 The Kubernetes Authors.
|
|
|
|
Licensed under the Apache License, Version 2.0 (the "License");
|
|
you may not use this file except in compliance with the License.
|
|
You may obtain a copy of the License at
|
|
|
|
http://www.apache.org/licenses/LICENSE-2.0
|
|
|
|
Unless required by applicable law or agreed to in writing, software
|
|
distributed under the License is distributed on an "AS IS" BASIS,
|
|
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
See the License for the specific language governing permissions and
|
|
limitations under the License.
|
|
*/
|
|
|
|
package operation
|
|
|
|
import "k8s.io/apimachinery/pkg/util/sets"
|
|
|
|
// Operation provides contextual information about a validation request and the API
|
|
// operation being validated.
|
|
// This type is intended for use with generate validation code and may be enhanced
|
|
// in the future to include other information needed to validate requests.
|
|
type Operation struct {
|
|
// Type is the category of operation being validated. This does not
|
|
// differentiate between HTTP verbs like PUT and PATCH, but rather merges
|
|
// those into a single "Update" category.
|
|
Type Type
|
|
|
|
// Options declare the options enabled for validation.
|
|
//
|
|
// Options should be set according to a resource validation strategy before validation
|
|
// is performed, and must be treated as read-only during validation.
|
|
//
|
|
// Options are identified by string names. Option string names may match the name of a feature
|
|
// gate, in which case the presence of the name in the set indicates that the feature is
|
|
// considered enabled for the resource being validated. Note that a resource may have a
|
|
// feature enabled even when the feature gate is disabled. This can happen when feature is
|
|
// already in-use by a resource, often because the feature gate was enabled when the
|
|
// resource first began using the feature.
|
|
//
|
|
// Unset options are disabled/false.
|
|
Options sets.Set[string]
|
|
}
|
|
|
|
// Code is the request operation to be validated.
|
|
type Type uint32
|
|
|
|
const (
|
|
// Create indicates the request being validated is for a resource create operation.
|
|
Create Type = iota
|
|
|
|
// Update indicates the request being validated is for a resource update operation.
|
|
Update
|
|
)
|