Merge pull request #31 from kubenow/feature/update-doc-tfvars

Rename terraform.tfvars to config.tfvars

Author: Marco Capuccini

advanced_topics/cloudflare-dns.rst

@@ -2,7 +2,7 @@ Cloudflare DNS Records
 ======================
 `Cloudflare <https://www.cloudflare.com>`_ runs one of the largest authoritative DNS networks in the world. In order to resolve domain names for exposed services, KubeNow can optionally configure the Cloudflare dynamic DNS service, so that a base domain name will resolve to the edge nodes (or the master node if no edge node is deployed).
 
-To configure the Cloudflare dynamic DNS service, it is sufficient to uncomment the following lines in the ``terraform.tfvars`` file, specifying credentials, domain and subdomain::
+To configure the Cloudflare dynamic DNS service, it is sufficient to uncomment the following lines in the ``config.tfvars`` file, specifying credentials, domain and subdomain::
 
   # Cloudflare configuration (optional)
   use_cloudflare = "true"

advanced_topics/cloudflare-proxied.rst

@@ -2,7 +2,7 @@ Cloudflare: Proxied Traffic
 ===========================
 Incoming container traffic can be optionally proxied through the `Cloudflare <https://www.cloudflare.com>`_ servers. When operating in this mode Cloudflare provides HTTPS for container services, and it protects against distributed denial of service, customer data breach and malicious bot abuse.
 
-To enable Cloudflare proxied traffic, it is sufficient to uncomment the following lines in the ``terraform.tfvars`` file, specifying DNS records to be proxied::
+To enable Cloudflare proxied traffic, it is sufficient to uncomment the following lines in the ``config.tfvars`` file, specifying DNS records to be proxied::
 
   # Cloudflare proxy (optional)
   cloudflare_proxied = "true"

advanced_topics/edge-nodes.rst

@@ -2,7 +2,7 @@ Edge Nodes
 ==========
 Edge nodes are specialized service nodes with an associated public IP address, and they run `Traefik <https://traefik.io>`_ acting as reverse proxies, and load balancers, for the services that are exposed to the Internet. In the default settings, we don't deploy any edge node enabling the reverse proxy logic in the master node instead. However, in production settings we recommend to deploy one or more edge nodes to reduce the load in the master.
 
-To deploy edge nodes, it is sufficient to uncomment the following lines in the ``terraform.tfvars`` file, and to set the desired number of edge nodes, along with an available instance flavor::
+To deploy edge nodes, it is sufficient to uncomment the following lines in the ``config.tfvars`` file, and to set the desired number of edge nodes, along with an available instance flavor::
 
   # Master configuration (mandatory in general, above all for single-server setup)
   master_flavor = "your-master-flavor"

advanced_topics/glusterfs-nodes.rst

@@ -2,7 +2,7 @@ GlusterFS Nodes
 ===============
 GlusterFS nodes are specialized service nodes. They run only `GlusterFS <https://www.gluster.org>`_ and they are attached to a block storage volume to provide additional capacity. In the default settings, we don't deploy GlusterFS nodes, as it is not required in many use cases. However, GlusterFS can be particularly convenient when a distributed file system is needed for container synchronization.
 
-To deploy GlusterFS nodes, it is sufficient to uncomment the following lines in the ``terraform.tfvars`` file, and to set the desired number of edge nodes, along with an available instance flavor and block storage disk size::
+To deploy GlusterFS nodes, it is sufficient to uncomment the following lines in the ``config.tfvars`` file, and to set the desired number of edge nodes, along with an available instance flavor and block storage disk size::
 
  # Gluster configuration
  glusternode_count = "1"

advanced_topics/single-node-deployments.rst

@@ -2,7 +2,7 @@ Single-Node Deployments
 =======================
 When resources are scarce, or for testing purpose, KubeNow enables single-node deployments. In fact, it is possible to deploy the master node only, which will automatically enabled for service scheduling.
 
-You can achieve this by commenting all of the lines for the other instance types (i.e. edge node, gluster node and worker node) in the ``terraform.tfvars`` file, leaving the master node only as it is shown below::
+You can achieve this by commenting all of the lines for the other instance types (i.e. edge node, gluster node and worker node) in the ``config.tfvars`` file, leaving the master node only as it is shown below::
 
     # Master configuration (mandatory in general, above all for single-server setup)
     master_flavor = "your-master-flavor"

getting_started/bootstrap.rst

@@ -28,7 +28,7 @@ Locate into ``my_deployment`` :
 
   cd my_deployment
 
-In the configuration file ``terraform.tfvars`` you will need to set at least:
+In the configuration file ``config.tfvars`` you will need to set at least:
 
 **Cluster configuration**
 
@@ -126,7 +126,7 @@ Locate into ``my_deployment`` :
 
   cd my_deployment
 
-In the configuration file ``terraform.tfvars`` you will need to set at least:
+In the configuration file ``config.tfvars`` you will need to set at least:
 
 **Cluster configuration**
 
@@ -193,7 +193,7 @@ Locate into ``my_deployment`` :
 
   cd my_deployment
 
-In the configuration file ``terraform.tfvars`` you will need to set at least:
+In the configuration file ``config.tfvars`` you will need to set at least:
 
 **Cluster configuration**
 
@@ -256,7 +256,7 @@ Locate into ``my_deployment`` :
 
   cd my_deployment
 
-In the configuration file ``terraform.tfvars`` you will need to set at least:
+In the configuration file ``config.tfvars`` you will need to set at least:
 
 **Cluster configuration**