@@ -3,7 +3,7 @@ apiVersion: apiextensions.k8s.io/v1
3
3
kind : CustomResourceDefinition
4
4
metadata :
5
5
annotations :
6
- controller-gen.kubebuilder.io/version : v0.16.1
6
+ controller-gen.kubebuilder.io/version : v0.14.0
7
7
name : integrationtestscenarios.appstudio.redhat.com
8
8
spec :
9
9
group : appstudio.redhat.com
@@ -158,8 +158,16 @@ spec:
158
158
properties :
159
159
conditions :
160
160
items :
161
- description : Condition contains details for one aspect of the current
162
- state of this API Resource.
161
+ description : " Condition contains details for one aspect of the current
162
+ state of this API Resource.\n ---\n This struct is intended for
163
+ direct use as an array at the field path .status.conditions. For
164
+ example,\n\n\n\t type FooStatus struct{\n\t // Represents the
165
+ observations of a foo's current state.\n\t // Known .status.conditions.type
166
+ are: \" Available\" , \" Progressing\" , and \" Degraded\"\n\t //
167
+ +patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
168
+ \ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\" conditions,omitempty\"
169
+ patchStrategy:\" merge\" patchMergeKey:\" type\" protobuf:\" bytes,1,rep,name=conditions\" `\n\n\n\t
170
+ \ // other fields\n\t }"
163
171
properties :
164
172
lastTransitionTime :
165
173
description : |-
@@ -200,7 +208,12 @@ spec:
200
208
- Unknown
201
209
type : string
202
210
type :
203
- description : type of condition in CamelCase or in foo.example.com/CamelCase.
211
+ description : |-
212
+ type of condition in CamelCase or in foo.example.com/CamelCase.
213
+ ---
214
+ Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
215
+ useful (see .node.status.conditions), the ability to deconflict is important.
216
+ The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
204
217
maxLength : 316
205
218
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])$
206
219
type : string
@@ -388,8 +401,16 @@ spec:
388
401
properties :
389
402
conditions :
390
403
items :
391
- description : Condition contains details for one aspect of the current
392
- state of this API Resource.
404
+ description : " Condition contains details for one aspect of the current
405
+ state of this API Resource.\n ---\n This struct is intended for
406
+ direct use as an array at the field path .status.conditions. For
407
+ example,\n\n\n\t type FooStatus struct{\n\t // Represents the
408
+ observations of a foo's current state.\n\t // Known .status.conditions.type
409
+ are: \" Available\" , \" Progressing\" , and \" Degraded\"\n\t //
410
+ +patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
411
+ \ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\" conditions,omitempty\"
412
+ patchStrategy:\" merge\" patchMergeKey:\" type\" protobuf:\" bytes,1,rep,name=conditions\" `\n\n\n\t
413
+ \ // other fields\n\t }"
393
414
properties :
394
415
lastTransitionTime :
395
416
description : |-
@@ -430,7 +451,12 @@ spec:
430
451
- Unknown
431
452
type : string
432
453
type :
433
- description : type of condition in CamelCase or in foo.example.com/CamelCase.
454
+ description : |-
455
+ type of condition in CamelCase or in foo.example.com/CamelCase.
456
+ ---
457
+ Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
458
+ useful (see .node.status.conditions), the ability to deconflict is important.
459
+ The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
434
460
maxLength : 316
435
461
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])$
436
462
type : string
@@ -560,8 +586,16 @@ spec:
560
586
properties :
561
587
conditions :
562
588
items :
563
- description : Condition contains details for one aspect of the current
564
- state of this API Resource.
589
+ description : " Condition contains details for one aspect of the current
590
+ state of this API Resource.\n ---\n This struct is intended for
591
+ direct use as an array at the field path .status.conditions. For
592
+ example,\n\n\n\t type FooStatus struct{\n\t // Represents the
593
+ observations of a foo's current state.\n\t // Known .status.conditions.type
594
+ are: \" Available\" , \" Progressing\" , and \" Degraded\"\n\t //
595
+ +patchMergeKey=type\n\t // +patchStrategy=merge\n\t // +listType=map\n\t
596
+ \ // +listMapKey=type\n\t Conditions []metav1.Condition `json:\" conditions,omitempty\"
597
+ patchStrategy:\" merge\" patchMergeKey:\" type\" protobuf:\" bytes,1,rep,name=conditions\" `\n\n\n\t
598
+ \ // other fields\n\t }"
565
599
properties :
566
600
lastTransitionTime :
567
601
description : |-
@@ -602,7 +636,12 @@ spec:
602
636
- Unknown
603
637
type : string
604
638
type :
605
- description : type of condition in CamelCase or in foo.example.com/CamelCase.
639
+ description : |-
640
+ type of condition in CamelCase or in foo.example.com/CamelCase.
641
+ ---
642
+ Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be
643
+ useful (see .node.status.conditions), the ability to deconflict is important.
644
+ The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt)
606
645
maxLength : 316
607
646
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])$
608
647
type : string
0 commit comments