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: 'APIVersion defines the versioned schema of this representation
35
+
of an object. Servers should convert recognized schemas to the latest
36
+
internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
37
+
type: string
38
+
kind:
39
+
description: 'Kind is a string value representing the REST resource this
40
+
object represents. Servers may infer this from the endpoint the client
41
+
submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
42
+
type: string
43
+
metadata:
44
+
type: object
45
+
spec:
46
+
description: CronSpec defines the desired state of Cron
47
+
properties:
48
+
concurrencyPolicy:
49
+
description: 'Specifies how to treat concurrent executions of a Task.
50
+
Valid values are: - "Allow" (default): allows CronJobs to run concurrently;
51
+
- "Forbid": forbids concurrent runs, skipping next run if previous
52
+
run hasn''t finished yet; - "Replace": cancels currently running
53
+
job and replaces it with a new one'
54
+
type: string
55
+
deadline:
56
+
description: Deadline is the timestamp that a cron job can keep scheduling
57
+
util then.
58
+
format: date-time
59
+
type: string
60
+
historyLimit:
61
+
description: The number of finished job history to retain. This is
62
+
a pointer to distinguish between explicit zero and not specified.
63
+
format: int32
64
+
type: integer
65
+
schedule:
66
+
description: The schedule in Cron format, see https://en.wikipedia.org/wiki/Cron.
67
+
type: string
68
+
suspend:
69
+
description: This flag tells the controller to suspend subsequent
70
+
executions, it does not apply to already started executions. Defaults
71
+
to false.
72
+
type: boolean
73
+
template:
74
+
description: Specifies the job that will be created when executing
75
+
a CronTask.
76
+
properties:
77
+
apiVersion:
78
+
description: 'APIVersion defines the versioned schema of this
79
+
representation of an object. Servers should convert recognized
80
+
schemas to the latest internal value, and may reject unrecognized
81
+
values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources'
82
+
type: string
83
+
kind:
84
+
description: 'Kind is a string value representing the REST resource
85
+
this object represents. Servers may infer this from the endpoint
86
+
the client submits requests to. Cannot be updated. In CamelCase.
87
+
More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds'
88
+
type: string
89
+
workload:
90
+
description: Workload is the specification of the desired cron
91
+
job with specific types.
92
+
type: object
93
+
x-kubernetes-preserve-unknown-fields: true
94
+
type: object
95
+
required:
96
+
- schedule
97
+
- template
98
+
type: object
99
+
status:
100
+
description: CronStatus defines the observed state of Cron
101
+
properties:
102
+
active:
103
+
description: A list of currently running jobs.
104
+
items:
105
+
description: 'ObjectReference contains enough information to let
106
+
you inspect or modify the referred object. --- New uses of this
107
+
type are discouraged because of difficulty describing its usage
108
+
when embedded in APIs. 1. Ignored fields. It includes many fields
109
+
which are not generally honored. For instance, ResourceVersion
110
+
and FieldPath are both very rarely valid in actual usage. 2.
111
+
Invalid usage help. It is impossible to add specific help for
112
+
individual usage. In most embedded usages, there are particular restrictions
113
+
like, "must refer only to types A and B" or "UID not honored"
114
+
or "name must be restricted". Those cannot be well described
115
+
when embedded. 3. Inconsistent validation. Because the usages
116
+
are different, the validation rules are different by usage, which
117
+
makes it hard for users to predict what will happen. 4. The fields
118
+
are both imprecise and overly precise. Kind is not a precise
119
+
mapping to a URL. This can produce ambiguity during interpretation
120
+
and require a REST mapping. In most cases, the dependency is
121
+
on the group,resource tuple and the version of the actual
122
+
struct is irrelevant. 5. We cannot easily change it. Because
123
+
this type is embedded in many locations, updates to this type will
124
+
affect numerous schemas. Don''t make new APIs embed an underspecified
125
+
API type they do not control. Instead of using this type, create
126
+
a locally provided and used type that is well-focused on your
127
+
reference. For example, ServiceReferences for admission registration:
0 commit comments