Update install_yamls_setup/README.md

Improve explaination about how to use the playbook using Ansible vault.

Author: weinimo

README.md

@@ -71,7 +71,7 @@ for integration.
 This project aims to follow the
 Kubernetes [Operator pattern](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/)
 
-It uses 
+It uses
 [Controllers](https://kubernetes.io/docs/concepts/architecture/controller/)
 which provides a reconcile function responsible for synchronizing resources
 untile the desired state is reached on the cluster

install_yamls_setup/README.md

@@ -14,14 +14,17 @@ defined:
     podman_quayio_user: <user>
     podman_quayio_password: <password>
 
-The recommended way to manage those secrets is using `ansible-vault`. Pay attention that
-`openshift_pull_secret` needs to be a string and hence the JSON data needs to be put in
-quotes.
+The recommended way to manage those secrets is using `ansible-vault`. Pay
+attention that `openshift_pull_secret` is put in quotes so that the
+JSON structure is stored as a string.
 
 ## Playbook
 
-The `playbook.yaml` file can be used for running the role. Create an
-inventory file (e.g. named `hosts`) to define the host(s). Then run the playbook
-like so:
+The `playbook.yaml` file can be used for running the role. Create an inventory
+file (e.g. named `hosts`) to define the host(s). Then run the playbook like so:
 
     ansible-playbook -i hosts -D playbook.yaml
+
+When using `ansible-vault` for storing secrets, additional vault specific
+arguments will need to be provided. When an encrypted variable file is used add
+the `-e @<filename>` argument.