Document semver and polling support for OCI-based HelmOps

This support is now visible in documentation for v0.14 and v0.13, where
it has recently been added.
This commit is contained in:
Corentin Néau 2025-08-18 15:58:10 +02:00
parent 3f319bd63d
commit 26fe2da9be
No known key found for this signature in database
GPG Key ID: 4E10825BFE040608
2 changed files with 6 additions and 2 deletions

View File

@ -81,7 +81,7 @@ bundle will be created, aborting deployment.
A Helm chart can also be referenced through its repository and chart name, with an optional version, which may be a A Helm chart can also be referenced through its repository and chart name, with an optional version, which may be a
static version or a version constraint. static version or a version constraint.
This is where polling can make sense, because referencing the chart using a repository allows Fleet to check the In this case, polling can make sense, because referencing the chart using a repository allows Fleet to check the
repository's `index.yaml` for available versions matching the `version` field. repository's `index.yaml` for available versions matching the `version` field.
Example: Example:
@ -114,6 +114,8 @@ and no bundle being created.
In this case, Fleet will be downloading OCI artifacts. This means that: In this case, Fleet will be downloading OCI artifacts. This means that:
* the `version` field represents an OCI artifact's tag, which may be different to the actual version of the * the `version` field represents an OCI artifact's tag, which may be different to the actual version of the
chart stored in the OCI artifact. chart stored in the OCI artifact.
* polling is supported: Fleet can check available OCI tags matching both the provided repository and version constraint
on a regular basis, configured through the polling interval.
* an OCI artifact may contain multiple Helm charts. This use case has only been validated with OCI artifacts containing * an OCI artifact may contain multiple Helm charts. This use case has only been validated with OCI artifacts containing
a single Helm chart. a single Helm chart.
::: :::

View File

@ -81,7 +81,7 @@ bundle will be created, aborting deployment.
A Helm chart can also be referenced through its repository and chart name, with an optional version, which may be a A Helm chart can also be referenced through its repository and chart name, with an optional version, which may be a
static version or a version constraint. static version or a version constraint.
This is where polling can make sense, because referencing the chart using a repository allows Fleet to check the In this case, polling can make sense, because referencing the chart using a repository allows Fleet to check the
repository's `index.yaml` for available versions matching the `version` field. repository's `index.yaml` for available versions matching the `version` field.
Example: Example:
@ -114,6 +114,8 @@ and no bundle being created.
In this case, Fleet will be downloading OCI artifacts. This means that: In this case, Fleet will be downloading OCI artifacts. This means that:
* the `version` field represents an OCI artifact's tag, which may be different to the actual version of the * the `version` field represents an OCI artifact's tag, which may be different to the actual version of the
chart stored in the OCI artifact. chart stored in the OCI artifact.
* polling is supported: Fleet can check available OCI tags matching both the provided repository and version constraint
on a regular basis, configured through the polling interval.
* an OCI artifact may contain multiple Helm charts. This use case has only been validated with OCI artifacts containing * an OCI artifact may contain multiple Helm charts. This use case has only been validated with OCI artifacts containing
a single Helm chart. a single Helm chart.
::: :::