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
|`concurrentReconciles`| concurrentReconciles is the concurrent reconcile number of the controller |`4`|
36
36
|`ignoreWorkflowWithoutControllerRequirement`| will determine whether to process the workflowrun without 'workflowrun.oam.dev/controller-version-require' annotation |`false`|
|`workflow.enableSuspendOnFailure`| Enable the capability of suspend an failed workflow automatically |`false`|
44
-
|`workflow.enablePatchStatusAtOnce`| Enable the capability of patch status at once |`false`|
45
-
|`workflow.enableWatchEventListener`| Enable the capability of watch event listener for a faster reconcile, note that you need to install [kube-trigger](https://github.com/kubevela/kube-trigger) first to use this feature |`false`|
46
-
|`workflow.backoff.maxTime.waitState`| The max backoff time of workflow in a wait condition |`60`|
47
-
|`workflow.backoff.maxTime.failedState`| The max backoff time of workflow in a failed condition |`300`|
48
-
|`workflow.step.errorRetryTimes`| The max retry times of a failed workflow step |`10`|
49
-
|`workflow.groupByLabel`| The label used to group workflow record |`pipeline.oam.dev/name`|
|`workflow.enableSuspendOnFailure`| Enable the capability of suspend an failed workflow automatically |`false`|
43
+
|`workflow.enablePatchStatusAtOnce`| Enable the capability of patch status at once |`false`|
44
+
|`workflow.enableWatchEventListener`| Enable the capability of watch event listener for a faster reconcile, note that you need to install [kube-trigger](https://github.com/kubevela/kube-trigger) first to use this feature |`false`|
45
+
|`workflow.enableExternalPackageForDefaultCompiler`| Enable external package for default compiler |`true`|
46
+
|`workflow.enableExternalPackageWatchForDefaultCompiler`| Enable external package watch for default compiler |`false`|
47
+
|`workflow.backoff.maxTime.waitState`| The max backoff time of workflow in a wait condition |`60`|
48
+
|`workflow.backoff.maxTime.failedState`| The max backoff time of workflow in a failed condition |`300`|
49
+
|`workflow.step.errorRetryTimes`| The max retry times of a failed workflow step |`10`|
50
+
|`workflow.groupByLabel`| The label used to group workflow record |`pipeline.oam.dev/name`|
description: WorkflowRun is the Schema for the workflowRun API
33
32
properties:
34
33
apiVersion:
35
-
description: 'APIVersion defines the versioned schema of this representation
36
-
of an object. Servers should convert recognized schemas to the latest
37
-
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
34
+
description: |-
35
+
APIVersion defines the versioned schema of this representation of an object.
36
+
Servers should convert recognized schemas to the latest internal value, and
37
+
may reject unrecognized values.
38
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
38
39
type: string
39
40
kind:
40
-
description: 'Kind is a string value representing the REST resource this
41
-
object represents. Servers may infer this from the endpoint the client
42
-
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
41
+
description: |-
42
+
Kind is a string value representing the REST resource this object represents.
43
+
Servers may infer this from the endpoint the client submits requests to.
44
+
Cannot be updated.
45
+
In CamelCase.
46
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
43
47
type: string
44
48
metadata:
45
49
type: object
@@ -211,13 +215,15 @@ spec:
211
215
description: A Condition that may apply to a resource.
212
216
properties:
213
217
lastTransitionTime:
214
-
description: LastTransitionTime is the last time this condition
215
-
transitioned from one status to another.
218
+
description: |-
219
+
LastTransitionTime is the last time this condition transitioned from one
220
+
status to another.
216
221
format: date-time
217
222
type: string
218
223
message:
219
-
description: A Message containing details about this condition's
220
-
last transition from one status to another, if any.
224
+
description: |-
225
+
A Message containing details about this condition's last transition from
226
+
one status to another, if any.
221
227
type: string
222
228
reason:
223
229
description: A Reason for this condition's last transition from
@@ -228,8 +234,9 @@ spec:
228
234
False, or Unknown?
229
235
type: string
230
236
type:
231
-
description: Type of this condition. At most one of each condition
232
-
type may apply to a resource at any point in time.
237
+
description: |-
238
+
Type of this condition. At most one of each condition type may apply to
239
+
a resource at any point in time.
233
240
type: string
234
241
required:
235
242
- lastTransitionTime
@@ -239,64 +246,66 @@ spec:
239
246
type: object
240
247
type: array
241
248
contextBackend:
242
-
description: "ObjectReference contains enough information to let you
243
-
inspect or modify the referred object. --- New uses of this type
244
-
are discouraged because of difficulty describing its usage when
245
-
embedded in APIs. 1. Ignored fields. It includes many fields which
246
-
are not generally honored. For instance, ResourceVersion and FieldPath
247
-
are both very rarely valid in actual usage. 2. Invalid usage help.
248
-
\ It is impossible to add specific help for individual usage. In
249
-
most embedded usages, there are particular restrictions like, \"must
250
-
refer only to types A and B\" or \"UID not honored\" or \"name must
251
-
be restricted\". Those cannot be well described when embedded. 3.
252
-
Inconsistent validation. Because the usages are different, the
253
-
validation rules are different by usage, which makes it hard for
254
-
users to predict what will happen. 4. The fields are both imprecise
255
-
and overly precise. Kind is not a precise mapping to a URL. This
256
-
can produce ambiguity during interpretation and require a REST mapping.
257
-
\ In most cases, the dependency is on the group,resource tuple and
258
-
the version of the actual struct is irrelevant. 5. We cannot easily
259
-
change it. Because this type is embedded in many locations, updates
260
-
to this type will affect numerous schemas. Don't make new APIs
261
-
embed an underspecified API type they do not control. \n Instead
262
-
of using this type, create a locally provided and used type that
263
-
is well-focused on your reference. For example, ServiceReferences
264
-
for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533
265
-
."
249
+
description: |-
250
+
ObjectReference contains enough information to let you inspect or modify the referred object.
251
+
---
252
+
New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
253
+
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.
254
+
2. Invalid usage help. It is impossible to add specific help for individual usage. In most embedded usages, there are particular
255
+
restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
256
+
Those cannot be well described when embedded.
257
+
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.
258
+
4. The fields are both imprecise and overly precise. Kind is not a precise mapping to a URL. This can produce ambiguity
259
+
during interpretation and require a REST mapping. In most cases, the dependency is on the group,resource tuple
260
+
and the version of the actual struct is irrelevant.
261
+
5. We cannot easily change it. Because this type is embedded in many locations, updates to this type
262
+
will affect numerous schemas. Don't make new APIs embed an underspecified API type they do not control.
263
+
264
+
265
+
Instead of using this type, create a locally provided and used type that is well-focused on your reference.
266
+
For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .
266
267
properties:
267
268
apiVersion:
268
269
description: API version of the referent.
269
270
type: string
270
271
fieldPath:
271
-
description: 'If referring to a piece of an object instead of
272
-
an entire object, this string should contain a valid JSON/Go
273
-
field access statement, such as desiredState.manifest.containers[2].
274
-
For example, if the object reference is to a container within
275
-
a pod, this would take on a value like: "spec.containers{name}"
276
-
(where "name" refers to the name of the container that triggered
277
-
the event) or if no container name is specified "spec.containers[2]"
278
-
(container with index 2 in this pod). This syntax is chosen
279
-
only to have some well-defined way of referencing a part of
280
-
an object. TODO: this design is not final and this field is
281
-
subject to change in the future.'
272
+
description: |-
273
+
If referring to a piece of an object instead of an entire object, this string
274
+
should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2].
275
+
For example, if the object reference is to a container within a pod, this would take on a value like:
276
+
"spec.containers{name}" (where "name" refers to the name of the container that triggered
277
+
the event) or if no container name is specified "spec.containers[2]" (container with
278
+
index 2 in this pod). This syntax is chosen only to have some well-defined way of
279
+
referencing a part of an object.
280
+
TODO: this design is not final and this field is subject to change in the future.
282
281
type: string
283
282
kind:
284
-
description: 'Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
283
+
description: |-
284
+
Kind of the referent.
285
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
285
286
type: string
286
287
name:
287
-
description: 'Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names'
288
+
description: |-
289
+
Name of the referent.
290
+
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
288
291
type: string
289
292
namespace:
290
-
description: 'Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/'
293
+
description: |-
294
+
Namespace of the referent.
295
+
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
291
296
type: string
292
297
resourceVersion:
293
-
description: 'Specific resourceVersion to which this reference
294
-
is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency'
298
+
description: |-
299
+
Specific resourceVersion to which this reference is made, if any.
300
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
295
301
type: string
296
302
uid:
297
-
description: 'UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids'
303
+
description: |-
304
+
UID of the referent.
305
+
More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids
0 commit comments