@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
3
3
kind : CustomResourceDefinition
4
4
metadata :
5
5
annotations :
6
- api-approved.kubernetes.io : " https://github.com/kubernetes-csi/external-snapshotter/pull/971 "
6
+ api-approved.kubernetes.io : " https://github.com/kubernetes-csi/external-snapshotter/pull/1068 "
7
7
controller-gen.kubebuilder.io/version : v0.12.0
8
8
creationTimestamp : null
9
9
name : volumegroupsnapshotcontents.groupsnapshot.storage.k8s.io
@@ -227,6 +227,24 @@ spec:
227
227
format : date-time
228
228
type : string
229
229
type : object
230
+ pvVolumeSnapshotContentRefList :
231
+ description : PVVolumeSnapshotContentRefList is the list of pairs of
232
+ PV and VolumeSnapshotCOntent for this group snapshot The maximum
233
+ number of allowed snapshots in the group is 100.
234
+ items :
235
+ description : PVVolumeSnapshotContentPair represent a pair of PV
236
+ names and VolumeSnapshotContent names
237
+ properties :
238
+ persistentVolumeName :
239
+ description : PersistentVolumeName is the name of the persistent
240
+ volume
241
+ type : string
242
+ volumeSnapshotContentName :
243
+ description : VolumeSnapshotContentName is the name of the volume
244
+ snapshot content resource
245
+ type : string
246
+ type : object
247
+ type : array
230
248
readyToUse :
231
249
description : ReadyToUse indicates if all the individual snapshots
232
250
in the group are ready to be used to restore a group of volumes.
@@ -239,72 +257,6 @@ spec:
239
257
system. If a storage system does not provide such an id, the CSI
240
258
driver can choose to return the VolumeGroupSnapshot name.
241
259
type : string
242
- volumeSnapshotContentRefList :
243
- description : VolumeSnapshotContentRefList is the list of volume snapshot
244
- content references for this group snapshot. The maximum number of
245
- allowed snapshots in the group is 100.
246
- items :
247
- description : " ObjectReference contains enough information to let
248
- you inspect or modify the referred object. --- New uses of this
249
- type are discouraged because of difficulty describing its usage
250
- when embedded in APIs. 1. Ignored fields. It includes many fields
251
- which are not generally honored. For instance, ResourceVersion
252
- and FieldPath are both very rarely valid in actual usage. 2. Invalid
253
- usage help. It is impossible to add specific help for individual
254
- usage. In most embedded usages, there are particular restrictions
255
- like, \" must refer only to types A and B\" or \" UID not honored\"
256
- or \" name must be restricted\" . Those cannot be well described
257
- when embedded. 3. Inconsistent validation. Because the usages
258
- are different, the validation rules are different by usage, which
259
- makes it hard for users to predict what will happen. 4. The fields
260
- are both imprecise and overly precise. Kind is not a precise
261
- mapping to a URL. This can produce ambiguity during interpretation
262
- and require a REST mapping. In most cases, the dependency is
263
- on the group,resource tuple and the version of the actual struct
264
- is irrelevant. 5. We cannot easily change it. Because this type
265
- is embedded in many locations, updates to this type will affect
266
- numerous schemas. Don't make new APIs embed an underspecified
267
- API type they do not control. \n Instead of using this type, create
268
- a locally provided and used type that is well-focused on your
269
- reference. For example, ServiceReferences for admission registration:
270
- https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
271
- ."
272
- properties :
273
- apiVersion :
274
- description : API version of the referent.
275
- type : string
276
- fieldPath :
277
- description : ' If referring to a piece of an object instead of
278
- an entire object, this string should contain a valid JSON/Go
279
- field access statement, such as desiredState.manifest.containers[2].
280
- For example, if the object reference is to a container within
281
- a pod, this would take on a value like: "spec.containers{name}"
282
- (where "name" refers to the name of the container that triggered
283
- the event) or if no container name is specified "spec.containers[2]"
284
- (container with index 2 in this pod). This syntax is chosen
285
- only to have some well-defined way of referencing a part of
286
- an object. TODO: this design is not final and this field is
287
- subject to change in the future.'
288
- type : string
289
- kind :
290
- description : ' Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
291
- type : string
292
- name :
293
- description : ' Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
294
- type : string
295
- namespace :
296
- description : ' Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
297
- type : string
298
- resourceVersion :
299
- description : ' Specific resourceVersion to which this reference
300
- is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
301
- type : string
302
- uid :
303
- description : ' UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
304
- type : string
305
- type : object
306
- x-kubernetes-map-type : atomic
307
- type : array
308
260
type : object
309
261
required :
310
262
- spec
0 commit comments