API Reference¶
Packages¶
k8s.v6d.io/v1alpha1
k8s.v6d.io/v1alpha1¶
Package v1alpha1 contains API Schema definitions for the k8s v1alpha1 API group
Resource Types¶
Backup¶
Backup describes a backup operation of vineyard objects, which uses the Kubernetes PersistentVolume to store the backup data. Every backup operation will be binded with the name of Backup.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
BackupList¶
BackupList contains a list of Backup
BackupSpec¶
BackupSpec defines the desired state of Backup
Appears in:
Field |
Description |
---|---|
|
the name of the vineyard cluster |
|
the namespace of the vineyard cluster |
|
the specific objects to be backed up if not specified, all objects will be backed up |
|
the path of backup data |
|
the PersistentVolumeSpec of the backup data |
|
the PersistentVolumeClaimSpec of the backup data |
CSIDriver¶
CSIDriver is the Schema for the csidrivers API
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
CSIDriverList¶
CSIDriverList contains a list of CSIDriver
CSIDriverSpec¶
CSIDriverSpec defines the desired state of CSIDriver
Appears in:
Field |
Description |
---|---|
|
Image is the name of the csi driver image |
|
ImagePullPolicy is the image pull policy of the csi driver |
|
StorageClassName is the name of the storage class |
|
VolumeBindingMode is the volume binding mode of the storage class |
|
Sidecar is the configuration for the CSI sidecar container nolint: lll |
|
Clusters are the list of vineyard clusters |
|
EnableToleration is the flag to enable toleration for the csi driver |
|
EnableVerboseLog is the flag to enable verbose log for the csi driver |
CSISidecar¶
CSISidecar holds the configuration for the CSI sidecar container
Appears in:
Field |
Description |
---|---|
|
ProvisionerImage is the image of the provisioner sidecar |
|
AttacherImage is the image of the attacher sidecar |
|
NodeRegistrarImage is the image of the node registrar sidecar |
|
LivenessProbeImage is the image of the liveness probe sidecar |
|
ImagePullPolicy is the image pull policy of all sidecar containers |
|
EnableTopology is the flag to enable topology for the csi driver |
GlobalObject¶
GlobalObject describes a global object in vineyard, whose metadata will be stored in etcd.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
GlobalObjectList¶
GlobalObjectList contains a list of GlobalObject
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
GlobalObjectSpec¶
GlobalObjectSpec defines the desired state of GlobalObject
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
LocalObject¶
LocalObject describes a local object in vineyard, whose metadata will only be stored in local vineyard.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
LocalObjectList¶
LocalObjectList contains a list of LocalObject
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
LocalObjectSpec¶
LocalObjectSpec defines the desired state of LocalObject
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
MetricConfig¶
MetricConfig holds the configuration about metric container
Appears in:
Field |
Description |
---|---|
|
Enable metrics |
|
represent the metric’s image |
|
the policy about pulling image |
Operation¶
Operation describes an operation between workloads, such as assembly and repartition.
As for the assembly
operation, there are several kinds of computing engines, some may not support the stream data, so we need to insert an assembly
operation to assemble the stream data into a batch data, so that the next computing engines can process the data.
As for the repartition
operation, the vineyard has integrated with the distributed computing engines, such as Dask. If you want to repartition the data to adapt the dask workers, then the repartition
operation is essential for such scenario.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
OperationList¶
OperationList contains a list of Operation
OperationSpec¶
OperationSpec defines the desired state of Operation
Appears in:
Field |
Description |
---|---|
|
the name of vineyard pluggable drivers, including assembly and repartition. |
|
the type of object, including local and distributed. |
|
the required job’s name of the operation |
|
the target job’s name of the operation |
|
TimeoutSeconds is the timeout of the operation. |
PluginImageConfig¶
PluginImageConfig holds all image configuration about pluggable drivers(backup, recover, local assembly, distributed assembly, repartition)
Appears in:
Field |
Description |
---|---|
|
the image of backup operation |
|
the image of recover operation |
|
the image of dask repartition operation |
|
the image of local assembly operation |
|
the image of distributed assembly operation |
Recover¶
Recover describes a recover operation of vineyard objects, which is used to recover a specific backup operation.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
RecoverList¶
RecoverList contains a list of Recover
RecoverSpec¶
RecoverSpec defines the desired state of Recover
Appears in:
Field |
Description |
---|---|
|
the name of backup |
|
the namespace of backup |
ServiceConfig¶
ServiceConfig holds all service configuration about vineyardd
Appears in:
Field |
Description |
---|---|
|
service type |
|
service port |
Sidecar¶
Sidecar is used for configuring and managing the vineyard sidecar container.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
SidecarList¶
SidecarList contains a list of Sidecar
SidecarSpec¶
SidecarSpec defines the desired state of Sidecar
Appears in:
Field |
Description |
---|---|
|
the selector of pod |
|
the replicas of workload |
|
EtcdReplicas describe the etcd replicas |
|
vineyard container configuration nolint: lll |
|
metric container configuration |
|
metric configurations |
|
rpc service configuration |
|
SecurityContext holds the security context settings for the vineyardd container. |
|
Volumes is the list of Kubernetes volumes that can be mounted by the vineyard container. |
|
VolumeMounts specifies the volumes listed in “.spec.volumes” to mount into the vineyard container. |
SpillConfig¶
SpillConfig holds all configuration about spilling
Appears in:
Field |
Description |
---|---|
|
the name of the spill config |
|
the path of spilling |
|
low watermark of spilling memory |
|
high watermark of triggering spilling |
|
the PersistentVolumeSpec of the spilling PV |
|
the PersistentVolumeClaimSpec of the spill file |
VineyardClusters¶
VineyardClusters contains the list of vineyard clusters
Appears in:
Field |
Description |
---|---|
|
Namespace is the namespace of the vineyard cluster |
|
Name is the name of the vineyard deployment |
VineyardConfig¶
VineyardConfig holds all configuration about vineyard container
Appears in:
Field |
Description |
---|---|
|
represent the vineyardd’s image |
|
the policy about pulling image |
|
synchronize CRDs when persisting objects |
|
The directory on host for the IPC socket file. The UNIX-domain socket will be placed as |
|
shared memory size for vineyardd |
|
reserve the shared memory for vineyardd |
|
memory threshold of streams (percentage of total memory) |
|
the configuration of spilling |
|
vineyard environment configuration |
|
the memory resources of vineyard container |
|
the cpu resources of vineyard container |
Vineyardd¶
Vineyardd is used to deploy a vineyard cluster on kubernetes, which can simplify the configurations of the vineyard binary, the external etcd cluster and the vineyard Deployment. As vineyard is bound to a specific socket on the hostpath by default, the vineyard pod cannot be deployed on the same node. Before deploying vineyardd, you should know how many nodes are available for vineyard pod to deploy on and make sure the vineyardd pod number is less than the number of available nodes.
Appears in:
Field |
Description |
---|---|
|
|
|
|
|
Refer to Kubernetes API documentation for fields of |
|
VineyarddList¶
VineyarddList contains a list of Vineyardd
VineyarddSpec¶
VineyarddSpec holds all configuration about vineyardd
Appears in:
Field |
Description |
---|---|
|
Replicas is the number of vineyardd pods to deploy |
|
EtcdReplicas describe the etcd replicas |
|
vineyardd’s service |
|
vineyard container configuration nolint: lll |
|
operation container configuration nolint: lll |
|
metric container configuration |
|
Volume configuration |
|
SecurityContext holds the security context settings for the vineyardd container. |
|
Volumes is the list of Kubernetes volumes that can be mounted by the vineyard deployment. |
|
VolumeMounts specifies the volumes listed in “.spec.volumes” to mount into the vineyard deployment. |
VolumeConfig¶
VolumeConfig holds all configuration about persistent volume
Appears in:
Field |
Description |
---|---|
|
the name of pvc |
|
the mount path of pv |