adding reference to HelmOps docs

This commit is contained in:
hridyesh bisht 2025-09-01 14:10:49 +05:30
parent 0b1630dd33
commit c57600c597
No known key found for this signature in database
GPG Key ID: 7E30EC522B3FCFBB
1 changed files with 3 additions and 0 deletions

View File

@ -9,11 +9,14 @@ Using OCI registries for Helm charts helps you:
* Push and pull charts using standard OCI commands, making them easy to distribute across environments. * Push and pull charts using standard OCI commands, making them easy to distribute across environments.
* Manage charts in registries designed for high availability and global distribution. * Manage charts in registries designed for high availability and global distribution.
For more information about HelmOps with OCI registry, refer to [HelmOps](helm-ops.md#oci-registry)
![A visual asset displaying flow of fetching Helm charts from an OCI registry](../static/img/fetch-Helm-from-OCI.svg) ![A visual asset displaying flow of fetching Helm charts from an OCI registry](../static/img/fetch-Helm-from-OCI.svg)
For example, if you manage multiple clusters with Fleet, developers can push Helm charts to an internal OCI registry. Fleet then pulls the charts directly from the registry and deploys them to downstream clusters. For example, if you manage multiple clusters with Fleet, developers can push Helm charts to an internal OCI registry. Fleet then pulls the charts directly from the registry and deploys them to downstream clusters.
This approach avoids maintaining a separate chart repository and reuses your existing registry infrastructure. This approach avoids maintaining a separate chart repository and reuses your existing registry infrastructure.
## Helm chart in fleet.yaml ## Helm chart in fleet.yaml
To fetch Helm chart, you reference the chart like this in a fleet.yaml file: To fetch Helm chart, you reference the chart like this in a fleet.yaml file: