spec: add note about jitter in interval sections
Signed-off-by: Hidde Beydals <hidde@hhh.computer>
This commit is contained in:
parent
e391c2fb88
commit
c65980ec63
|
@ -224,6 +224,11 @@ e.g. `10m0s` to reconcile the object every 10 minutes.
|
|||
If the `.metadata.generation` of a resource changes (due to e.g. a change to
|
||||
the spec), this is handled instantly outside the interval window.
|
||||
|
||||
**Note:** The controller can be configured to apply a jitter to the interval in
|
||||
order to distribute the load more evenly when multiple GitRepository objects are
|
||||
set up with the same interval. For more information, please refer to the
|
||||
[source-controller configuration options](https://fluxcd.io/flux/components/source/options/).
|
||||
|
||||
### Timeout
|
||||
|
||||
`.spec.timeout` is an optional field to specify a timeout for Git operations
|
||||
|
|
|
@ -724,7 +724,7 @@ Where the (base64 decoded) value of `.data.serviceaccount` looks like this:
|
|||
|
||||
### Interval
|
||||
|
||||
`.spec.interval` is a required field that specifices the interval which the
|
||||
`.spec.interval` is a required field that specifies the interval which the
|
||||
object storage bucket must be consulted at.
|
||||
|
||||
After successfully reconciling a Bucket object, the source-controller requeues
|
||||
|
@ -733,7 +733,12 @@ the object for inspection after the specified interval. The value must be in a
|
|||
e.g. `10m0s` to look at the object storage bucket every 10 minutes.
|
||||
|
||||
If the `.metadata.generation` of a resource changes (due to e.g. the apply of a
|
||||
change to the spec), this is handled instantly outside of the interval window.
|
||||
change to the spec), this is handled instantly outside the interval window.
|
||||
|
||||
**Note:** The controller can be configured to apply a jitter to the interval in
|
||||
order to distribute the load more evenly when multiple Bucket objects are set up
|
||||
with the same interval. For more information, please refer to the
|
||||
[source-controller configuration options](https://fluxcd.io/flux/components/source/options/).
|
||||
|
||||
### Endpoint
|
||||
|
||||
|
|
|
@ -45,7 +45,7 @@ In the above example:
|
|||
|
||||
You can run this example by saving the manifest into `helmchart.yaml`.
|
||||
|
||||
**NOTE:** HelmChart is usually used by the helm-controller. Based on the
|
||||
**Note:** HelmChart is usually used by the helm-controller. Based on the
|
||||
HelmRelease configuration, an associated HelmChart is created by the
|
||||
helm-controller.
|
||||
|
||||
|
@ -211,7 +211,7 @@ changes in a `HelmRepository`. `Revision` is used for creating a new artifact
|
|||
when the source revision changes in a `GitRepository` or a `Bucket` Source. It
|
||||
defaults to `ChartVersion`.
|
||||
|
||||
**NOTE:** If the reconcile strategy is `ChartVersion` and the source reference
|
||||
**Note:** If the reconcile strategy is `ChartVersion` and the source reference
|
||||
is a `GitRepository` or a `Bucket`, no new chart artifact is produced on updates
|
||||
to the source unless the `version` in `Chart.yaml` is incremented. To produce
|
||||
new chart artifact on change in source revision, set the reconcile strategy to
|
||||
|
@ -233,6 +233,11 @@ e.g. `10m0s` to look at the source for updates every 10 minutes.
|
|||
If the `.metadata.generation` of a resource changes (due to e.g. applying a
|
||||
change to the spec), this is handled instantly outside the interval window.
|
||||
|
||||
**Note:** The controller can be configured to apply a jitter to the interval in
|
||||
order to distribute the load more evenly when multiple HelmChart objects are set
|
||||
up with the same interval. For more information, please refer to the
|
||||
[source-controller configuration options](https://fluxcd.io/flux/components/source/options/).
|
||||
|
||||
### Suspend
|
||||
|
||||
`.spec.suspend` is an optional field to suspend the reconciliation of a
|
||||
|
|
|
@ -361,6 +361,11 @@ e.g. `10m0s` to fetch the HelmRepository index YAML every 10 minutes.
|
|||
If the `.metadata.generation` of a resource changes (due to e.g. applying a
|
||||
change to the spec), this is handled instantly outside the interval window.
|
||||
|
||||
**Note:** The controller can be configured to apply a jitter to the interval in
|
||||
order to distribute the load more evenly when multiple HelmRepository objects
|
||||
are set up with the same interval. For more information, please refer to the
|
||||
[source-controller configuration options](https://fluxcd.io/flux/components/source/options/).
|
||||
|
||||
### URL
|
||||
|
||||
`.spec.url` is a required field that depending on the [type of the HelmRepository object](#type)
|
||||
|
|
|
@ -355,6 +355,11 @@ e.g. `10m0s` to reconcile the object every 10 minutes.
|
|||
If the `.metadata.generation` of a resource changes (due to e.g. a change to
|
||||
the spec), this is handled instantly outside the interval window.
|
||||
|
||||
**Note:** The controller can be configured to apply a jitter to the interval in
|
||||
order to distribute the load more evenly when multiple OCIRepository objects are
|
||||
set up with the same interval. For more information, please refer to the
|
||||
[source-controller configuration options](https://fluxcd.io/flux/components/source/options/).
|
||||
|
||||
### Timeout
|
||||
|
||||
`.spec.timeout` is an optional field to specify a timeout for OCI operations
|
||||
|
|
Loading…
Reference in New Issue