MySQL Private IP configurations require a special peering between your VPC network and a VPC managed by Google. The module supports creating such a peering.
It is sufficient to instantiate this module once for all MySQL instances that are connected to the same VPC.
NOTE: See the linked documentation for all requirements for accessing a MySQL instance via its Private IP.
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| address | First IP address of the IP range to allocate to CLoud SQL instances and other Private Service Access services. If not set, GCP will pick a valid one for you. | string |
"" |
no |
| description | An optional description of the Global Address resource. | string |
"" |
no |
| ip_version | IP Version for the allocation. Can be IPV4 or IPV6. | string |
"" |
no |
| labels | The key/value labels for the IP range allocated to the peered network. | map(string) |
{} |
no |
| prefix_length | Prefix length of the IP range reserved for Cloud SQL instances and other Private Service Access services. Defaults to /16. | number |
16 |
no |
| project_id | The project ID of the VPC network to peer. This can be a shared VPC host projec. | string |
n/a | yes |
| vpc_network | Name of the VPC network to peer. | string |
n/a | yes |
| Name | Description |
|---|---|
| address | First IP of the reserved range. |
| google_compute_global_address_name | URL of the reserved range. |
| peering_completed | Use for enforce ordering between resource creation |