You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PVVolumeSnapshotContentList is the list of pairs of PV and
282
+
VolumeSnapshotContent for this group snapshot
283
+
The maximum number of allowed snapshots in the group is 100.
284
+
items:
285
+
description: |-
286
+
PVVolumeSnapshotContentPair represent a pair of PV names and
287
+
VolumeSnapshotContent names
288
+
properties:
289
+
persistentVolumeRef:
290
+
description: PersistentVolumeRef is a reference to the persistent
291
+
volume resource
292
+
properties:
293
+
name:
294
+
description: |-
295
+
Name of the referent.
296
+
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
297
+
TODO: Add other useful fields. apiVersion, kind, uid?
298
+
type: string
299
+
type: object
300
+
x-kubernetes-map-type: atomic
301
+
volumeSnapshotContentRef:
302
+
description: VolumeSnapshotContentRef is a reference to the
303
+
volume snapshot content resource
304
+
properties:
305
+
name:
306
+
description: |-
307
+
Name of the referent.
308
+
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
309
+
TODO: Add other useful fields. apiVersion, kind, uid?
310
+
type: string
311
+
type: object
312
+
x-kubernetes-map-type: atomic
313
+
type: object
314
+
type: array
279
315
readyToUse:
280
316
description: |-
281
317
ReadyToUse indicates if all the individual snapshots in the group are ready to be
@@ -289,73 +325,6 @@ spec:
289
325
If a storage system does not provide such an id, the
290
326
CSI driver can choose to return the VolumeGroupSnapshot name.
291
327
type: string
292
-
volumeSnapshotContentRefList:
293
-
description: |-
294
-
VolumeSnapshotContentRefList is the list of volume snapshot content references
295
-
for this group snapshot.
296
-
The maximum number of allowed snapshots in the group is 100.
297
-
items:
298
-
description: |-
299
-
ObjectReference contains enough information to let you inspect or modify the referred object.
300
-
---
301
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
302
-
1. Ignored fields. It includes many fields which are not generally honored. For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage.
303
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
304
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
305
-
Those cannot be well described when embedded.
306
-
3. Inconsistent validation. Because the usages are different, the validation rules are different by usage, which makes it hard for users to predict what will happen.
307
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
308
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
309
-
and the version of the actual struct is irrelevant.
310
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
311
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
312
-
313
-
314
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
315
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
316
-
properties:
317
-
apiVersion:
318
-
description: API version of the referent.
319
-
type: string
320
-
fieldPath:
321
-
description: |-
322
-
If referring to a piece of an object instead of an entire object, this string
323
-
should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2].
324
-
For example, if the object reference is to a container within a pod, this would take on a value like:
325
-
"spec.containers{name}" (where "name" refers to the name of the container that triggered
326
-
the event) or if no container name is specified "spec.containers[2]" (container with
327
-
index 2 in this pod). This syntax is chosen only to have some well-defined way of
328
-
referencing a part of an object.
329
-
TODO: this design is not final and this field is subject to change in the future.
330
-
type: string
331
-
kind:
332
-
description: |-
333
-
Kind of the referent.
334
-
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
335
-
type: string
336
-
name:
337
-
description: |-
338
-
Name of the referent.
339
-
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
340
-
type: string
341
-
namespace:
342
-
description: |-
343
-
Namespace of the referent.
344
-
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
345
-
type: string
346
-
resourceVersion:
347
-
description: |-
348
-
Specific resourceVersion to which this reference is made, if any.
349
-
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
350
-
type: string
351
-
uid:
352
-
description: |-
353
-
UID of the referent.
354
-
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
0 commit comments