raspbernetes / k8s-cluster-installation

Bootstrap a k8s cluster with Ansible
https://raspbernetes.github.io/
Apache License 2.0
114 stars 32 forks source link

update infra gcp docs #102

Closed xunholy closed 3 years ago

xunholy commented 3 years ago

Signed-off-by: Michael Fornaro 20387402+xUnholy@users.noreply.github.com

Description

Please provide a description for what this PR is for.

Checklist

Issue Ref (Optional)

Which issue(s) this PR fixes (optional, using fixes #(, fixes #, ...) format, will close the issue(s) when the PR gets merged): Fixes #

Notes

Add special notes for your reviewer here.

github-actions[bot] commented 3 years ago

Terraform Format and Style 🖌success

Terraform Initialization ⚙️success

Terraform Validation 🤖Success! The configuration is valid.

Terraform Plan 📖success

Show Plan ```terraform Refreshing Terraform state in-memory prior to plan... The refreshed state will be used to calculate this plan, but will not be persisted to local or remote state storage. google_compute_network.vpc: Refreshing state... [id=projects/raspbernetes/global/networks/raspbernetes-vpc] google_compute_subnetwork.subnet: Refreshing state... [id=projects/raspbernetes/regions/us-central1/subnetworks/raspbernetes-subnet] google_container_cluster.primary: Refreshing state... [id=projects/raspbernetes/locations/us-central1/clusters/raspbernetes-gke] google_container_node_pool.primary_nodes: Refreshing state... [id=projects/raspbernetes/locations/us-central1/clusters/raspbernetes-gke/nodePools/raspbernetes-gke-node-pool] ------------------------------------------------------------------------ No changes. Infrastructure is up-to-date. This means that Terraform did not detect any differences between your configuration and real physical resources that exist. As a result, no actions need to be performed. ```

Pusher: @xUnholy, Action: pull_request, Working Directory: infrastructure/gcp, Workflow: terraform-plan