* bump provider versions to 5.0.0 * fix cloud run, logging and vpc-sc * Fix secret manager * fix gke nodepool * fix gke multitenant stage and blueprint * Moving alloydb module to experimental. * Add project to bare resources in examples * tfdoc * fix svpc blueprint test * Revert "fix svpc blueprint test" This reverts commit 14f02659098070136e64ead600580dd52c23c339. * Fix GKE peering project * Disable tests in alloydb module * Bring back secret ids in secret manager tests * Remove duplicate key * last push --------- Co-authored-by: Julio Castillo <jccb@google.com> |
||
---|---|---|
.. | ||
dev | ||
README.md |
README.md
GKE Multitenant stage
This directory contains a stage that can be used to centralize management of GKE multinenant clusters.
The Terraform code follows the same general approach used for the project factory and data platform stages, where a "fat module" contains the stage code and is used by thin code wrappers that localize it for each environment or specialized configuration:
The dev
folder contains an example setup for a generic development environment, and can be used as-is or cloned to implement other environments, or more specialized setups
Refer to the dev
documentation configuration details, and to the gke-serverless
documentation for the architectural design and decisions taken.