3535 spec :
3636 properties :
3737 bucketAccessRequest :
38- type : string
38+ description : ' ObjectReference contains enough information to let you
39+ inspect or modify the referred object. --- New uses of this type
40+ are discouraged because of difficulty describing its usage when
41+ embedded in APIs. 1. Ignored fields. It includes many fields which
42+ are not generally honored. For instance, ResourceVersion and FieldPath
43+ are both very rarely valid in actual usage. 2. Invalid usage help. It
44+ is impossible to add specific help for individual usage. In most
45+ embedded usages, there are particular restrictions like, "must
46+ refer only to types A and B" or "UID not honored" or "name must
47+ be restricted". Those cannot be well described when embedded. 3.
48+ Inconsistent validation. Because the usages are different, the
49+ validation rules are different by usage, which makes it hard for
50+ users to predict what will happen. 4. The fields are both imprecise
51+ and overly precise. Kind is not a precise mapping to a URL. This
52+ can produce ambiguity during interpretation and require a REST
53+ mapping. In most cases, the dependency is on the group,resource
54+ tuple and the version of the actual struct is irrelevant. 5.
55+ We cannot easily change it. Because this type is embedded in many
56+ locations, updates to this type will affect numerous schemas. Don'' t
57+ make new APIs embed an underspecified API type they do not control.
58+ Instead of using this type, create a locally provided and used type
59+ that is well-focused on your reference. For example, ServiceReferences
60+ for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
61+ .'
62+ properties :
63+ apiVersion :
64+ description : API version of the referent.
65+ type : string
66+ fieldPath :
67+ description : ' If referring to a piece of an object instead of
68+ an entire object, this string should contain a valid JSON/Go
69+ field access statement, such as desiredState.manifest.containers[2].
70+ For example, if the object reference is to a container within
71+ a pod, this would take on a value like: "spec.containers{name}"
72+ (where "name" refers to the name of the container that triggered
73+ the event) or if no container name is specified "spec.containers[2]"
74+ (container with index 2 in this pod). This syntax is chosen
75+ only to have some well-defined way of referencing a part of
76+ an object. TODO: this design is not final and this field is
77+ subject to change in the future.'
78+ type : string
79+ kind :
80+ description : ' Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
81+ type : string
82+ name :
83+ description : ' Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
84+ type : string
85+ namespace :
86+ description : ' Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
87+ type : string
88+ resourceVersion :
89+ description : ' Specific resourceVersion to which this reference
90+ is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
91+ type : string
92+ uid :
93+ description : ' UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
94+ type : string
95+ type : object
3996 bucketInstanceName :
4097 type : string
4198 mintedSecretName :
@@ -51,7 +108,64 @@ spec:
51108 provisioner :
52109 type : string
53110 serviceAccount :
54- type : string
111+ description : ' ObjectReference contains enough information to let you
112+ inspect or modify the referred object. --- New uses of this type
113+ are discouraged because of difficulty describing its usage when
114+ embedded in APIs. 1. Ignored fields. It includes many fields which
115+ are not generally honored. For instance, ResourceVersion and FieldPath
116+ are both very rarely valid in actual usage. 2. Invalid usage help. It
117+ is impossible to add specific help for individual usage. In most
118+ embedded usages, there are particular restrictions like, "must
119+ refer only to types A and B" or "UID not honored" or "name must
120+ be restricted". Those cannot be well described when embedded. 3.
121+ Inconsistent validation. Because the usages are different, the
122+ validation rules are different by usage, which makes it hard for
123+ users to predict what will happen. 4. The fields are both imprecise
124+ and overly precise. Kind is not a precise mapping to a URL. This
125+ can produce ambiguity during interpretation and require a REST
126+ mapping. In most cases, the dependency is on the group,resource
127+ tuple and the version of the actual struct is irrelevant. 5.
128+ We cannot easily change it. Because this type is embedded in many
129+ locations, updates to this type will affect numerous schemas. Don'' t
130+ make new APIs embed an underspecified API type they do not control.
131+ Instead of using this type, create a locally provided and used type
132+ that is well-focused on your reference. For example, ServiceReferences
133+ for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
134+ .'
135+ properties :
136+ apiVersion :
137+ description : API version of the referent.
138+ type : string
139+ fieldPath :
140+ description : ' If referring to a piece of an object instead of
141+ an entire object, this string should contain a valid JSON/Go
142+ field access statement, such as desiredState.manifest.containers[2].
143+ For example, if the object reference is to a container within
144+ a pod, this would take on a value like: "spec.containers{name}"
145+ (where "name" refers to the name of the container that triggered
146+ the event) or if no container name is specified "spec.containers[2]"
147+ (container with index 2 in this pod). This syntax is chosen
148+ only to have some well-defined way of referencing a part of
149+ an object. TODO: this design is not final and this field is
150+ subject to change in the future.'
151+ type : string
152+ kind :
153+ description : ' Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
154+ type : string
155+ name :
156+ description : ' Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
157+ type : string
158+ namespace :
159+ description : ' Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
160+ type : string
161+ resourceVersion :
162+ description : ' Specific resourceVersion to which this reference
163+ is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
164+ type : string
165+ uid :
166+ description : ' UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
167+ type : string
168+ type : object
55169 type : object
56170 status :
57171 properties :
0 commit comments