@@ -53,13 +53,60 @@ spec:
53
53
bucketClassName :
54
54
type : string
55
55
bucketRequest :
56
+ description : ' ObjectReference contains enough information to let you
57
+ inspect or modify the referred object. --- New uses of this type
58
+ are discouraged because of difficulty describing its usage when
59
+ embedded in APIs. 1. Ignored fields. It includes many fields which
60
+ are not generally honored. For instance, ResourceVersion and FieldPath
61
+ are both very rarely valid in actual usage. 2. Invalid usage help. It
62
+ is impossible to add specific help for individual usage. In most
63
+ embedded usages, there are particular restrictions like, "must
64
+ refer only to types A and B" or "UID not honored" or "name must
65
+ be restricted". Those cannot be well described when embedded. 3.
66
+ Inconsistent validation. Because the usages are different, the
67
+ validation rules are different by usage, which makes it hard for
68
+ users to predict what will happen. 4. The fields are both imprecise
69
+ and overly precise. Kind is not a precise mapping to a URL. This
70
+ can produce ambiguity during interpretation and require a REST
71
+ mapping. In most cases, the dependency is on the group,resource
72
+ tuple and the version of the actual struct is irrelevant. 5.
73
+ We cannot easily change it. Because this type is embedded in many
74
+ locations, updates to this type will affect numerous schemas. Don'' t
75
+ make new APIs embed an underspecified API type they do not control.
76
+ Instead of using this type, create a locally provided and used type
77
+ that is well-focused on your reference. For example, ServiceReferences
78
+ for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
79
+ .'
56
80
properties :
81
+ apiVersion :
82
+ description : API version of the referent.
83
+ type : string
84
+ fieldPath :
85
+ description : ' If referring to a piece of an object instead of
86
+ an entire object, this string should contain a valid JSON/Go
87
+ field access statement, such as desiredState.manifest.containers[2].
88
+ For example, if the object reference is to a container within
89
+ a pod, this would take on a value like: "spec.containers{name}"
90
+ (where "name" refers to the name of the container that triggered
91
+ the event) or if no container name is specified "spec.containers[2]"
92
+ (container with index 2 in this pod). This syntax is chosen
93
+ only to have some well-defined way of referencing a part of
94
+ an object. TODO: this design is not final and this field is
95
+ subject to change in the future.'
96
+ type : string
97
+ kind :
98
+ description : ' Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
99
+ type : string
57
100
name :
58
101
description : ' Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
59
102
type : string
60
103
namespace :
61
104
description : ' Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
62
105
type : string
106
+ resourceVersion :
107
+ description : ' Specific resourceVersion to which this reference
108
+ is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
109
+ type : string
63
110
uid :
64
111
description : ' UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
65
112
type : string
0 commit comments