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
The reason for the condition's last transition in CamelCase.
343
343
The specific API may choose whether or not this field is considered a guaranteed API.
344
-
This field may not be empty.
344
+
This field may be empty.
345
345
type: string
346
346
severity:
347
347
description: |-
348
-
Severity provides an explicit classification of Reason code, so the users or machines can immediately
348
+
severity provides an explicit classification of Reason code, so the users or machines can immediately
349
349
understand the current situation and act accordingly.
350
350
The Severity field MUST be set only when Status=False.
351
351
type: string
352
352
status:
353
-
description: Status of the condition, one of True, False, Unknown.
353
+
description: status of the condition, one of True, False, Unknown.
354
354
type: string
355
355
type:
356
356
description: |-
357
-
Type of condition in CamelCase or in foo.example.com/CamelCase.
357
+
type of condition in CamelCase or in foo.example.com/CamelCase.
358
358
Many .condition.type values are consistent across resources like Available, but because arbitrary conditions
359
359
can be useful (see .node.status.conditions), the ability to deconflict is important.
360
360
type: string
@@ -368,24 +368,8 @@ spec:
368
368
description: MatchingClusters is the list of references to Clusters
369
369
selected by the ClusterSelector.
370
370
items:
371
-
description: |-
372
-
ObjectReference contains enough information to let you inspect or modify the referred object.
373
-
---
374
-
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
375
-
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.
376
-
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
377
-
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
378
-
Those cannot be well described when embedded.
379
-
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.
380
-
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
381
-
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
382
-
and the version of the actual struct is irrelevant.
383
-
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
384
-
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
385
-
386
-
387
-
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
388
-
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
371
+
description: ObjectReference contains enough information to let
372
+
you inspect or modify the referred object.
389
373
properties:
390
374
apiVersion:
391
375
description: API version of the referent.
@@ -399,7 +383,6 @@ spec:
399
383
the event) or if no container name is specified "spec.containers[2]" (container with
400
384
index 2 in this pod). This syntax is chosen only to have some well-defined way of
401
385
referencing a part of an object.
402
-
TODO: this design is not final and this field is subject to change in the future.
0 commit comments