e372b50d19
* GKE Hub initial PR commit
* variable management adjust
* comments, fixes and alphabetically ordered variables
* Update README.md
* Update README.md
* Update README.md
* fix test
* resources vs modules
still needs some love
* remove modules usage
* comments, readme update and output
* adjusting outputs and README
* fix README.md
* fix README
* adjusted based on comments
still need some love in the google_gke_hub_feature_membership variables management
* types and variable management
* optionally enable required api
* Update README.md
* reorder locals and use standard formatting
* Don't enable services from modules
* Use self links for member clusters
* Update readme
* members_clusters back to map
@juliocc let's talk about this cause we saw it together in our call and if I change it to a list than the other resources are not going to work, they need location there too.
* Forcing null feature to false due to a bug in provider
If a block is set to null the provider will crash with a "panic: interface conversion: interface {} is nil, not map[string]interface {}" a PR will follow
* Readme update
* Readme.md update
* Update README.md
* bring back tolist, WIP
* Update main.tf
* Readme.md update
* Update README.md
* Update main.tf
* Update main.tf
* Add id and self_links output to gke-cluster
* Use try and make all member feature blocks dynamic/optional
* Change member clusters to map
* Add gke-hub tests
* Address PR comments
* Update gke-hub readme
Co-authored-by: Ludovico Magnocavallo <ludomagno@google.com>
Co-authored-by: Julio Castillo <jccb@google.com>
|
||
|---|---|---|
| .github/workflows | ||
| assets/logos | ||
| examples | ||
| fast | ||
| modules | ||
| tests | ||
| tools | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| MANIFESTO.md | ||
| README.md | ||
| REFERENCES.md | ||
| default-versions.tf | ||
| stages.png | ||
README.md
Terraform Examples and Modules for Google Cloud
This repository provides end-to-end examples and a suite of Terraform modules for Google Cloud, which support different use cases:
- organization-wide landing zone blueprint used to bootstrap real-world cloud foundations
- reference examples used to deep dive on network patterns or product features
- a comprehensive source of lean modules that lend themselves well to changes
The whole repository is meant to be cloned as a single unit, and then forked into separate owned repositories to seed production usage, or used as-is and periodically updated as a complete toolkit for prototyping. You can read more on this approach in our manifesto.
Organization blueprint (Fabric FAST)
Setting up a production-ready GCP organization is often a time-consuming process. Fabric FAST aims to speed up this process via two complementary goals. On the one hand, FAST provides a design of a GCP organization that includes the typical elements required by enterprise customers. Secondly, we provide a reference implementation of the FAST design using Terraform.
Modules
The suite of modules in this repository are designed for rapid composition and reuse, and to be reasonably simple and readable so that they can be forked and changed where use of third party code and sources is not allowed.
All modules share a similar interface where each module tries to stay close to the underlying provider resources, support IAM together with resource creation and modification, offer the option of creating multiple resources where it makes sense (eg not for projects), and be completely free of side-effects (eg no external commands).
The current list of modules supports most of the core foundational and networking components used to design end-to-end infrastructure, with more modules in active development for specialized compute, security, and data scenarios.
Currently available modules:
- foundational - folder, organization, project, service accounts, logging bucket, billing budget, naming convention
- networking - VPC, VPC firewall, VPC peering, VPN static, VPN dynamic, VPN HA, NAT, address reservation, DNS, L4 ILB, Service Directory, Cloud Endpoints
- compute - VM/VM group, MIG, GKE cluster, GKE nodepool, COS container (coredns, mysql, onprem, squid)
- data - GCS, BigQuery dataset, Pub/Sub, Datafusion, Bigtable instance, Cloud SQL instance, Data Catalog Policy Tag
- development - Cloud Source Repository, Container Registry, Artifact Registry, Apigee Organization, Apigee X Instance, API Gateway
- security - KMS, SecretManager, VPC Service Control
- serverless - Cloud Function, Cloud Run
For more information and usage examples see each module's README file.
End-to-end examples
The examples in this repository are split in several main sections: foundational examples that bootstrap the organizational hierarchy and automation prerequisites, networking examples that implement core patterns or features, data solutions examples that demonstrate how to integrate data services in complete scenarios, cloud operations examples that leverage specific products to meet specific operational needs and factories that implement resource factories for the repetitive creation of specific resources.