From 4fb96d4061d5fbb972c6251b91a7979fbba44955 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Corentin=20N=C3=A9au?= Date: Fri, 5 Sep 2025 11:31:27 +0200 Subject: [PATCH] Add note on auth for HelmOps This simply references gitOps docs on auth, but at least clarifies that HelmOps does support auth. --- docs/helm-ops.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/helm-ops.md b/docs/helm-ops.md index 7f8531f33..3c8d81ea0 100644 --- a/docs/helm-ops.md +++ b/docs/helm-ops.md @@ -147,6 +147,14 @@ When polling is enabled, Fleet does the following at the configured interval: * with `false` with an error if a failure happened * updating the `Last Polling Time` field to the starting time of the last polling attempt, even if it failed. +## Using private Helm repositories + +This works the same way as it does for gitOps, by referencing a Helm access secret through field `helmSecretName`. + +See [the gitOps docs](./gitrepo-add.md#using-private-helm-repositories) for more details. +The part on using separate credentials for each path is not relevant though, since unlike a GitRepo, a HelmOp resource +only references a single Helm chart. + ## Status updates Creating a HelmOp resource leads to a bundle being created, if Helm options are valid and a chart version can be found.