Fixing some typos
This commit is contained in:
Alejandro Leal
parent
f173a9cf25
commit
ea0de3adbb
|
|
@ -24,7 +24,7 @@ If the network_config variable is not provided, one VPC will be created in each
|
|||
|
||||
## Deploy your environment
|
||||
|
||||
We assume the identiy running the following steps has the following role:
|
||||
We assume the identity running the following steps has the following role:
|
||||
|
||||
- resourcemanager.projectCreator in case a new project will be created.
|
||||
- owner on the project in case you use an existing project.
|
||||
|
|
|
|||
|
|
@ -36,7 +36,7 @@ Once the resources have been created, do the following to verify that everything
|
|||
|
||||
kubectl apply -f tenant-setup.yaml
|
||||
|
||||
By applying that manifest thw following is created:
|
||||
By applying that manifest the following is created:
|
||||
|
||||
* A namespace called "apis". This is the namespace where the application will be deployed.
|
||||
* A Role and a RoleBinding in previously created namespace so the service account that has been configured for the CD pipeline trigger in Cloud Build is able to deploy the kubernetes application to that namespace.
|
||||
|
|
|
|||
|
|
@ -83,7 +83,7 @@ By default, the design assumes the following:
|
|||
- cross-environment traffic and traffic from any untrusted network to any trusted network (and vice versa) pass through the NVAs. For demo purposes, the current NVA performs simple routing/natting only
|
||||
- any traffic from a trusted network to an untrusted network (e.g. Internet) is natted by the NVAs. Users can configure further exclusions
|
||||
|
||||
The trusted landing VPC acts as a hub: it bridges internal resources with the outside world and it hosts the shared services consumed by the spoke VPCs, connected to the hub thorugh VPC network peerings. Spokes are used to partition the environments. By default:
|
||||
The trusted landing VPC acts as a hub: it bridges internal resources with the outside world and it hosts the shared services consumed by the spoke VPCs, connected to the hub through VPC network peerings. Spokes are used to partition the environments. By default:
|
||||
|
||||
- one spoke VPC hosts the development environment resources
|
||||
- one spoke VPC hosts the production environment resources
|
||||
|
|
|
|||
|
|
@ -37,6 +37,7 @@ The final number of subnets, and their IP addressing will depend on the user-spe
|
|||
- [Design overview and choices](#design-overview-and-choices)
|
||||
- [Multi-regional deployment](#multi-regional-deployment)
|
||||
- [VPC design](#vpc-design)
|
||||
- [NCC, NVAs and BGP sessions](#ncc-nvas-and-bgp-sessions)
|
||||
- [External connectivity](#external-connectivity)
|
||||
- [Internal connectivity](#internal-connectivity)
|
||||
- [IP ranges, subnetting, routing](#ip-ranges-subnetting-routing)
|
||||
|
|
@ -105,7 +106,7 @@ By default, the design assumes that:
|
|||
- cross-spoke (environment) traffic and traffic from any untrusted network to any trusted network (and vice versa) pass through the NVAs.
|
||||
- any traffic from a trusted network to an untrusted network (e.g. Internet) is natted by the NVAs. Users can configure further exclusions.
|
||||
|
||||
The trusted landing VPC acts as a hub: it bridges internal resources with the outside world and it hosts the shared services consumed by the spoke VPCs, connected to the hub thorugh VPC network peerings. Spokes are used to partition the environments. By default:
|
||||
The trusted landing VPC acts as a hub: it bridges internal resources with the outside world and it hosts the shared services consumed by the spoke VPCs, connected to the hub through VPC network peerings. Spokes are used to partition the environments. By default:
|
||||
|
||||
- one spoke VPC hosts the development environment resources
|
||||
- one spoke VPC hosts the production environment resources
|
||||
|
|
|
|||
|
|
@ -246,7 +246,7 @@ module "bigtable-instance" {
|
|||
| name | description | sensitive |
|
||||
|---|---|:---:|
|
||||
| [id](outputs.tf#L17) | Fully qualified instance id. | |
|
||||
| [instance](outputs.tf#L26) | BigTable intance. | |
|
||||
| [instance](outputs.tf#L26) | BigTable instance. | |
|
||||
| [table_ids](outputs.tf#L35) | Map of fully qualified table ids keyed by table name. | |
|
||||
| [tables](outputs.tf#L40) | Table resources. | |
|
||||
|
||||
|
|
|
|||
|
|
@ -80,7 +80,7 @@ output "filtered-projects" {
|
|||
| name | description | type | required | default |
|
||||
|---|---|:---:|:---:|:---:|
|
||||
| [parent](variables.tf#L55) | Parent folder or organization in 'folders/folder_id' or 'organizations/org_id' format. | <code>string</code> | ✓ | |
|
||||
| [ignore_folders](variables.tf#L17) | A list of folder IDs or numbers to be excluded from the output, all the subfolders and projects are exluded from the output regardless of the include_projects variable. | <code>list(string)</code> | | <code>[]</code> |
|
||||
| [ignore_folders](variables.tf#L17) | A list of folder IDs or numbers to be excluded from the output, all the subfolders and projects are excluded from the output regardless of the include_projects variable. | <code>list(string)</code> | | <code>[]</code> |
|
||||
| [ignore_projects](variables.tf#L28) | A list of project IDs, numbers or prefixes to exclude matching projects from the module output. | <code>list(string)</code> | | <code>[]</code> |
|
||||
| [include_projects](variables.tf#L41) | A list of project IDs/numbers to include to the output if some of them are excluded by `ignore_projects` wildcard entries. | <code>list(string)</code> | | <code>[]</code> |
|
||||
| [query](variables.tf#L64) | A string query as defined in the [Query Syntax](https://cloud.google.com/asset-inventory/docs/query-syntax). | <code>string</code> | | <code>"state:ACTIVE"</code> |
|
||||
|
|
|
|||
Loading…
Reference in New Issue