Commit 74d3963c authored by Arie Peterson's avatar Arie Peterson

Clarify flux/helm-operator communication in docs

parent 29afac07
......@@ -179,10 +179,10 @@ don't want to wait for that after making a change, you can trigger an update:
$ fluxctl --k8s-fwd-ns=oas sync
If there are any changes to `HelmRelease` manifests, these should be
subsequently picked up by `helm-operator` more or less instantly (though the
actual installation or upgrade could take quite a while, depending on what
needs to be done).
If there are any changes to `HelmRelease` manifests, `helm-operator` is
notified of that through the Kubernetes API and should act on them more or
less instantly (though the actual installation or upgrade could take quite a
while, depending on what needs to be done).
* If, for some reason, the `HelmRelease` manifests are still in sync between git
repository and cluster, but you'd still like to let `helm-operator` check
whether these `HelmRelease`s match what's actually installed, you can force
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment