Skip to content

Commit

Permalink
chore: generate updates
Browse files Browse the repository at this point in the history
  • Loading branch information
@gansheer @squakez
gansheer authored and squakez committed Feb 1, 2024
1 parent 3d5829c commit eb5057e
Show file tree
Hide file tree
Showing 15 changed files with 106 additions and 8 deletions.
6 changes: 6 additions & 0 deletions config/crd/bases/camel.apache.org_integrationkits.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,12 @@ spec:
description: The builder trait is internally used to determine
the best strategy to build and configure IntegrationKits.
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
12 changes: 12 additions & 0 deletions config/crd/bases/camel.apache.org_integrationplatforms.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -510,6 +510,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down Expand Up @@ -2364,6 +2370,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions config/crd/bases/camel.apache.org_integrations.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6417,6 +6417,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions config/crd/bases/camel.apache.org_kameletbindings.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6699,6 +6699,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to
use for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions config/crd/bases/camel.apache.org_pipes.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6697,6 +6697,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to
use for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
9 changes: 9 additions & 0 deletions docs/modules/ROOT/partials/apis/camel-k-crds.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5953,6 +5953,13 @@ map[string]string
Defines a set of nodes the builder pod is eligible to be scheduled on, based on labels on the node.
|`annotations` +
map[string]string
|
When using `pod` strategy, annotation to use for the builder pod.
|===
Expand Down Expand Up @@ -6157,6 +6164,8 @@ in order to save resources when the integration does not need to be executed.
Integrations that start from the following components are evaluated by the cron trait: `timer`, `cron`, `quartz`.
WARNING: In case of native build-mode defined in xref:traits:quarkus.adoc[quarkus] trait, the component can't be customized.
The rules for using a Kubernetes CronJob are the following:
- `timer`: when period is set in milliseconds with no remaining seconds, for example 120000. If there is any second left as in 121000 (120s and 1s) or the presence of any of these parameters (delay, repeatCount, time) then a CronJob won't be created, but a standard deployment.
Expand Down
4 changes: 4 additions & 0 deletions docs/modules/traits/pages/builder.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,10 @@ if you need to execute them. Useful only with `pod` strategy.
| map[string]string
| Defines a set of nodes the builder pod is eligible to be scheduled on, based on labels on the node.

| builder.annotations
| map[string]string
| When using `pod` strategy, annotation to use for the builder pod.

|===

// End of autogenerated code - DO NOT EDIT! (configuration)
Expand Down
2 changes: 2 additions & 0 deletions docs/modules/traits/pages/cron.adoc
View file
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,8 @@ in order to save resources when the integration does not need to be executed.

Integrations that start from the following components are evaluated by the cron trait: `timer`, `cron`, `quartz`.

WARNING: In case of native build-mode defined in xref:traits:quarkus.adoc[quarkus] trait, the component can't be customized.

The rules for using a Kubernetes CronJob are the following:

- `timer`: when period is set in milliseconds with no remaining seconds, for example 120000. If there is any second left as in 121000 (120s and 1s) or the presence of any of these parameters (delay, repeatCount, time) then a CronJob won't be created, but a standard deployment.
Expand Down
6 changes: 6 additions & 0 deletions helm/camel-k/crds/crd-integration-kit.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -201,6 +201,12 @@ spec:
description: The builder trait is internally used to determine
the best strategy to build and configure IntegrationKits.
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
12 changes: 12 additions & 0 deletions helm/camel-k/crds/crd-integration-platform.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -510,6 +510,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down Expand Up @@ -2364,6 +2370,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions helm/camel-k/crds/crd-integration.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6417,6 +6417,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to use
for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions helm/camel-k/crds/crd-kamelet-binding.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6699,6 +6699,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to
use for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
6 changes: 6 additions & 0 deletions helm/camel-k/crds/crd-pipe.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6697,6 +6697,12 @@ spec:
builder:
description: The configuration of Builder trait
properties:
annotations:
additionalProperties:
type: string
description: When using `pod` strategy, annotation to
use for the builder pod.
type: object
baseImage:
description: Specify a base image
type: string
Expand Down
7 changes: 7 additions & 0 deletions pkg/apis/camel/v1/trait/zz_generated.deepcopy.go
View file

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

20 changes: 12 additions & 8 deletions resources/traits.yaml
View file
Original file line number Diff line number Diff line change
Expand Up @@ -309,6 +309,9 @@ traits:
type: map[string]string
description: Defines a set of nodes the builder pod is eligible to be scheduled
on, based on labels on the node.
- name: annotations
type: map[string]string
description: When using `pod` strategy, annotation to use for the builder pod.
- name: camel
platform: true
profiles:
Expand Down Expand Up @@ -396,14 +399,15 @@ traits:
For such tasks, the cron trait can materialize the integration as a Kubernetes
CronJob instead of a standard deployment, in order to save resources when the
integration does not need to be executed. Integrations that start from the following
components are evaluated by the cron trait: `timer`, `cron`, `quartz`. The rules
for using a Kubernetes CronJob are the following: - `timer`: when period is set
in milliseconds with no remaining seconds, for example 120000. If there is any
second left as in 121000 (120s and 1s) or the presence of any of these parameters
(delay, repeatCount, time) then a CronJob won''t be created, but a standard deployment.
- `cron`, `quartz`: when the cron expression does not contain seconds (or the
"seconds" part is set to 0). E.g. `cron:tab?schedule=0/2${plus}*{plus}*{plus}*{plus}?`
or `quartz:trigger?cron=0{plus}0/2{plus}*{plus}*{plus}*{plus}?`.'
components are evaluated by the cron trait: `timer`, `cron`, `quartz`. WARNING:
In case of native build-mode defined in xref:traits:quarkus.adoc[quarkus] trait,
the component can''t be customized. The rules for using a Kubernetes CronJob are
the following: - `timer`: when period is set in milliseconds with no remaining
seconds, for example 120000. If there is any second left as in 121000 (120s and
1s) or the presence of any of these parameters (delay, repeatCount, time) then
a CronJob won''t be created, but a standard deployment. - `cron`, `quartz`: when
the cron expression does not contain seconds (or the "seconds" part is set to
0). E.g. `cron:tab?schedule=0/2${plus}*{plus}*{plus}*{plus}?` or `quartz:trigger?cron=0{plus}0/2{plus}*{plus}*{plus}*{plus}?`.'
properties:
- name: enabled
type: bool
Expand Down

0 comments on commit eb5057e

Please sign in to comment.