docs: updated docs (#121)

Signed-off-by: Ales Verbic <[email protected]>

Author: verbotenj

README.md

@@ -27,15 +27,15 @@ fined-grained instructions. Bootstrap and Stage 0 are optional if you bring your
 | Stage 2   | Shared services workload setup | [docs](stage2/README.md)    |
 | Stage 3   | Extensions setup               | [docs](stage3/README.md)    |
 
-
 ### Quick Start
 
 The fastest way to configure your cluster is using the `bin/bootstrap-cloud` script.
 Out of the box, this will configure a local `k3d` cluster. To configure a default
 cluster in AWS in the us-west-2 region, you only need to provide two configuration
-items.
+items or GCP in us-central1.
 
 config.yaml:
+
 ```yaml
 cloud_provider: aws
 cloudflared_token: eyJhI...
@@ -66,6 +66,7 @@ First, configure the `config.yaml` file as you would for bootstrap, but you must
 also include the correct information for the Terraform bucket created by bootstrap.
 
 config.yaml:
+
 ```yaml
 cloud_provider: aws
 cloudflared_token: eyJhI...

config.yaml.example

@@ -15,6 +15,9 @@ terraform_project_id: <project_id>
 terraform_state_bucket: pre-configured-bucket
 terraform_state_region: eu-central-1
 
+# GCP specific configuration
+terraform_state_kmskey: <kms_key_id>
+
 # Overrides for defaults for configuring a cluster using bootstrap and stage0/aws-terraform in AWS. These override the defaults
 # in common/defaults.yaml
 azs: [eu-central-1b, eu-central-1c]

stage1/README.md

@@ -12,7 +12,7 @@ Stage 1 of the bootstrap procedure is responsible for setting up static resource
 
 ### Define your Terraform backend
 
-Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. For example:
+Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. If you run `bin/bootstrap-cloud` the `backend.tf` should be automatically generated. For example AWS S3 backend configuration:
 
 ```tf
 terraform {

stage2/README.md

@@ -12,7 +12,7 @@ Stage 2 of the bootstrap procedure is responsible for setting up active workload
 
 ### Define your Terraform backend
 
-Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. For example:
+Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. If you run `bin/bootstrap-cloud` the `backend.tf` should be automatically generated. For example AWS S3 backend configuration:
 
 ```tf
 terraform {
@@ -62,4 +62,4 @@ The execution of the command might take a while depending on the specific cluste
 
 ## Next Steps
 
-You're done with stage 2. You can continue with [Stage 3](../stage3/README.md)
+You're done with stage 2. You can continue with [Stage 3](../stage3/README.md)

stage3/README.md

@@ -12,7 +12,7 @@ Stage 3 of the bootstrap procedure is responsible for setting up any use-case sp
 
 ### Define your Terraform backend
 
-Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. For example:
+Add a `backend.tf` file in the stage1 directory and include your particular backend configuration. If you run `bin/bootstrap-cloud` the `backend.tf` should be automatically generated. For example AWS S3 backend configuration:
 
 ```tf
 terraform {
@@ -63,4 +63,4 @@ The execution of the command might take a while depending on the specific cluste
 
 ## Next Steps
 
-You're done with cluster provisioning! You can start using your Demeter instance.
+You're done with cluster provisioning! You can start using your Demeter instance.