Skip to content

Commit 1329f80

Browse files
authored
Add conditions array to OperatorGroup v1 status (#133)
It is not possible to report condition/error information due to lacking of appropriate field in OperatorGroup status. This commit will add conditions array to OperatorGroup v1 status and it will be the place to report relevant information regarding operational conditions or errors that OperatorGroup may encounter during sync process. Signed-off-by: Vu Dinh <[email protected]>
1 parent db8dead commit 1329f80

File tree

4 files changed

+60
-1
lines changed

4 files changed

+60
-1
lines changed

crds/operators.coreos.com_operatorgroups.yaml

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -86,6 +86,50 @@ spec:
8686
required:
8787
- lastUpdated
8888
properties:
89+
conditions:
90+
description: Conditions is an array of the OperatorGroup's conditions.
91+
type: array
92+
items:
93+
description: "Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: \"Available\", \"Progressing\", and \"Degraded\" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:\"conditions,omitempty\" patchStrategy:\"merge\" patchMergeKey:\"type\" protobuf:\"bytes,1,rep,name=conditions\"` \n // other fields }"
94+
type: object
95+
required:
96+
- lastTransitionTime
97+
- message
98+
- reason
99+
- status
100+
- type
101+
properties:
102+
lastTransitionTime:
103+
description: lastTransitionTime is the last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.
104+
type: string
105+
format: date-time
106+
message:
107+
description: message is a human readable message indicating details about the transition. This may be an empty string.
108+
type: string
109+
maxLength: 32768
110+
observedGeneration:
111+
description: observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance.
112+
type: integer
113+
format: int64
114+
minimum: 0
115+
reason:
116+
description: reason contains a programmatic identifier indicating the reason for the condition's last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty.
117+
type: string
118+
maxLength: 1024
119+
minLength: 1
120+
pattern: ^[A-Za-z]([A-Za-z0-9_,:]*[A-Za-z0-9_])?$
121+
status:
122+
description: status of the condition, one of True, False, Unknown.
123+
type: string
124+
enum:
125+
- "True"
126+
- "False"
127+
- Unknown
128+
type:
129+
description: type of condition in CamelCase or in foo.example.com/CamelCase. --- Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
130+
type: string
131+
maxLength: 316
132+
pattern: ^([a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*/)?(([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9])$
89133
lastUpdated:
90134
description: LastUpdated is a timestamp of the last time the OperatorGroup's status was Updated.
91135
type: string

0 commit comments

Comments
 (0)