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
description: A list of pointers to currently running jobs.
204
204
items:
205
-
description: |-
206
-
ObjectReference contains enough information to let you inspect or modify the referred object.
207
-
---
208
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
209
-
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.
210
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
211
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
212
-
Those cannot be well described when embedded.
213
-
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.
214
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
215
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
216
-
and the version of the actual struct is irrelevant.
217
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
218
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
219
-
220
-
221
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
222
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
205
+
description: ObjectReference contains enough information to let
206
+
you inspect or modify the referred object.
223
207
properties:
224
208
apiVersion:
225
209
description: API version of the referent.
@@ -233,7 +217,6 @@ spec:
233
217
the event) or if no container name is specified "spec.containers[2]" (container with
234
218
index 2 in this pod). This syntax is chosen only to have some well-defined way of
235
219
referencing a part of an object.
236
-
TODO: this design is not final and this field is subject to change in the future.
List of objects depended by this object. If this image is managed by a controller,
117
117
then an entry in this list will point to this controller.
118
118
items:
119
-
description: |-
120
-
ObjectReference contains enough information to let you inspect or modify the referred object.
121
-
---
122
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
123
-
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.
124
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
125
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
126
-
Those cannot be well described when embedded.
127
-
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.
128
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
129
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
130
-
and the version of the actual struct is irrelevant.
131
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
132
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
133
-
134
-
135
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
136
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
119
+
description: ObjectReference contains enough information
120
+
to let you inspect or modify the referred object.
137
121
properties:
138
122
apiVersion:
139
123
description: API version of the referent.
@@ -147,7 +131,6 @@ spec:
147
131
the event) or if no container name is specified "spec.containers[2]" (container with
148
132
index 2 in this pod). This syntax is chosen only to have some well-defined way of
149
133
referencing a part of an object.
150
-
TODO: this design is not final and this field is subject to change in the future.
151
134
type: string
152
135
kind:
153
136
description: |-
@@ -220,7 +203,6 @@ spec:
220
203
concurrency, change detection, and the watch operation on a resource or set of resources.
221
204
Clients must treat these values as opaque and passed unmodified back to the server.
0 commit comments