changes for introduce a reclaim policy for ephemerally created Volume resources

Author: ushabelgur

api/storage/v1alpha1/volume_types.go

@@ -123,8 +123,24 @@ type VolumeList struct {
 	Items           []Volume `json:"items"`
 }
 
+// ReclaimPolicy for a Volume tells what to do with the volume after its managing resource has been deleted
+type ReclaimPolicy string
+
+const (
+	// The Volume resource is not deleted after the managing resource has been deleted
+	Retain ReclaimPolicy = "Retain"
+	// The Volume resource is garbage-collected when the managing resource has been deleted
+	Delete ReclaimPolicy = "Delete"
+)
+
+type EphemeralVolumeSpec struct {
+	VolumeSpec `json:",inline"`
+	// ReclaimPolicy defines the strategy for the corresponding volume resource after its managing resource has been deleted
+	ReclaimPolicy ReclaimPolicy `json:"reclaimpolicy,omitempty"`
+}
+
 // VolumeTemplateSpec is the specification of a Volume template.
 type VolumeTemplateSpec struct {
 	metav1.ObjectMeta `json:"metadata,omitempty"`
-	Spec              VolumeSpec `json:"spec,omitempty"`
+	Spec              EphemeralVolumeSpec `json:"spec,omitempty"`
 }

api/storage/v1alpha1/zz_generated.deepcopy.go

@@ -54,6 +54,7 @@ API rule violation: names_match,github.com/ironcore-dev/ironcore/api/networking/
 API rule violation: names_match,github.com/ironcore-dev/ironcore/api/networking/v1alpha1,NetworkInterfaceSpec,IPs
 API rule violation: names_match,github.com/ironcore-dev/ironcore/api/networking/v1alpha1,NetworkInterfaceStatus,IPs
 API rule violation: names_match,github.com/ironcore-dev/ironcore/api/networking/v1alpha1,NetworkSpec,PeeringClaimRefs
+API rule violation: names_match,github.com/ironcore-dev/ironcore/api/storage/v1alpha1,EphemeralVolumeSpec,ReclaimPolicy
 API rule violation: names_match,k8s.io/api/core/v1,AzureDiskVolumeSource,DataDiskURI
 API rule violation: names_match,k8s.io/api/core/v1,ContainerStatus,LastTerminationState
 API rule violation: names_match,k8s.io/api/core/v1,DaemonEndpoint,Port