Explain what is synced to git by Flux
@@ -72,7 +72,7 @@ daemon and point them at different repos. If you do this, consider
trimming the RBAC permissions you give each daemon's service account.
This
-[flux (daemon) operator](https://github.com/justinbarrick/flux-operator)
+[Flux (daemon) operator](https://github.com/justinbarrick/flux-operator)
project may be of use for managing multiple daemons.
### Do I have to put my application code and config in the same git repo?
@@ -94,10 +94,22 @@ Kubernetes, use `--git-path` to constrain where Flux starts looking.
See also [requirements.md](./requirements.md) for a little more
explanation.
-### Why does Flux need a deploy key?
+### Why does Flux need a git ssh key with write access?
-Flux needs a deploy key to be allowed to push to the version control
-system in order to read and update the manifests.
+There are a number of Flux commands and API calls which will update the git repo in the course of
+applying the command. This is done to ensure that git remains the single source of truth.
+
+For example, if you use the following `fluxctl` command:
+
+ fluxctl release --controller=deployment/foo --update-image=bar:v2
+
+The image tag will be updated in the git repository upon applying the command.
+
+For more information about flux commands see [the fluxctl docs](./using.md).
+
+### Does Flux automatically sync changes back to git?
+
+No. It applies changes to git only when a Flux command or API call makes them.
### How do I give Flux access to an image registry?
