Merge branch '872-document-which-flux-version-to-use' into 'master'

Resolve "Document which `flux` version to use"

Closes #872

See merge request openappstack/openappstack!455

docs/installation_instructions.rst

@@ -56,7 +56,8 @@ be run on the provisioning machine, unless specified otherwise:
   (``apt install python3-pip python3-dev git`` on Debian)
 - ``ssh-agent`` to give you access to your VPS
 - ``kubectl`` (`installation instructions <https://kubernetes.io/docs/tasks/tools/#kubectl>`__)
-- ``flux`` (`installation instructions <https://fluxcd.io/docs/installation/#install-the-flux-cli>`__)
+- ``flux version 0.14.2`` Download from: https://github.com/fluxcd/flux2/releases/download/v0.14.2/flux_0.14.2_linux_amd64.tar.gz
+
 - We recommend using a `python
   virtualenv <https://docs.python.org/3/tutorial/venv.html>`__ to make
   sure we do not change any of your other projects. Install virtualenv
@@ -308,8 +309,8 @@ sure 'ping' shows your VPS's IP address:
 
     $ ping oas.example.org
 
-The ``install`` command will try to log into your machine as the
-``root``\ user using SSH.
+The ``install`` command will try to log into your machine as the ``root``\ user
+using SSH.
 
 Run the ``install`` command with the CLI to completely configure your VPS for
 OpenAppStack.
@@ -377,6 +378,13 @@ to install:
 - Velero with ``install-velero.sh`` (only if you have configured it in
   :ref:`backups-with-velero`).
 
+When the installation scripts complete, the application installation may still
+be running on the OpenAppStack cluster. You can monitor the progress by running
+``flux get kustomizations`` (use ``watch flux get kustomizations`` to get
+updates). If all kustomizations have been applied correctly, you can monitor
+specific application releases by running ``watch flux get helmreleases
+--all-namespaces``.
+
 .. _step-6:
 
 Step 6: Validate setup

docs/troubleshooting.rst

@@ -310,7 +310,7 @@ You can `grep` for your cluster domain or for any specific subdomain to narrow
 down results.
 
 Example
-'''''''
+~~~~~~~
 
 Query for failed certificates, -requests, challenges or orders:
 

install/flux-version-check.sh

+if [ "$(flux --version)" != "flux version 0.14.2" ]; then
+    echo "The OpenAppStack installation only works with Flux version 0.14.2"
+    exit 1;
+fi

install/install-nextcloud.sh

@@ -2,6 +2,8 @@
 
 set -euo pipefail
 
+. $(dirname "$0")/flux-version-check.sh
+
 # This kustomization's only purpose is to add the kustomization that is in the
 # flxu2/cluster/optional/nextcloud folder. After this kustomization is applied
 # an `add-nextcloud` kustomization will be present on the cluster, as well as a

install/install-openappstack.sh

@@ -2,6 +2,8 @@
 
 set -euo pipefail
 
+. $(dirname "$0")/flux-version-check.sh
+
 flux install \
   --network-policy=false \
   --watch-all-namespaces=true \

install/install-rocketchat.sh

@@ -2,6 +2,8 @@
 
 set -euo pipefail
 
+. $(dirname "$0")/flux-version-check.sh
+
 # This kustomization's only purpose is to add the kustomization that is in the
 # flxu2/cluster/optional/rocketchat folder. After this kustomization is applied
 # an `add-rocketchat` kustomization will be present on the cluster, as well as a

install/install-velero.sh

@@ -2,6 +2,8 @@
 
 set -euo pipefail
 
+. $(dirname "$0")/flux-version-check.sh
+
 # This kustomization's only purpose is to add the kustomization that is in the
 # flxu2/cluster/optional/velero folder. After this kustomization is applied
 # an `add-velero` kustomization will be present on the cluster, as well as a

install/install-wordpress.sh

@@ -2,6 +2,8 @@
 
 set -euo pipefail
 
+. $(dirname "$0")/flux-version-check.sh
+
 # This kustomization's only purpose is to add the kustomization that is in the
 # flxu2/cluster/optional/wordpress folder. After this kustomization is applied
 # an `add-wordpress` kustomization will be present on the cluster, as well as a