You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request.
Please do not leave +1 or me too comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
If an issue is assigned to a user, that user is claiming responsibility for the issue.
Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.
Description
The documentation states that the networks block has..
Network - (Required) The name of the GCE VPC network to which the instance is connected
Community Note
Description
The documentation states that the networks block has..
Network - (Required) The name of the GCE VPC network to which the instance is connected
In a shared VPC configuration this MUST be the ID and not just the name in the format projects/HOST_PROJECT_ID/global/networks/SHARED_VPC_NAME (ref https://cloud.google.com/filestore/docs/shared-vpc#create-filestore-on-vpc)
reserved_ip_range - (Optional) A /29 CIDE block that identifies the range of IP addresses reserved for this instance.
If using PRIVATE_SERVICE_ACCESS for connect_mode this MUST specify the NAME of the network range and not the CIDR directly.
I think this could really help people attempting to deploy this service for the first time to update the documentation to cover this.
New or Affected Resource(s)
Potential Terraform Configuration
n/a
References
https://cloud.google.com/filestore/docs/shared-vpc#create-filestore-on-vpc
The text was updated successfully, but these errors were encountered: