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
If the CIDR block values for your HVN and VPCs overlap, then you will not be able to establish a connection. Ensure that any VPCs you plan to connect do not have overlapping values.
The default HVN CIDR block value does not overlap with the default CIDR block value for AWS VPCs (172.31.0.0/16). However, if you are planning to use this HVN in production, we recommend adding a custom value instead of using the default.
Should it be update to include/mention Azure VNets or make the verbiage a bit more generic like "your cloud provider network" or something of the sort so it covers, AWS, Azure and future cloud providers too?
New or Affected Resource(s)
hcp_hvn
Community Note
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
The hcp_hvn resource page currently mentions the below:
If the CIDR block values for your HVN and VPCs overlap, then you will not be able to establish a connection. Ensure that any VPCs you plan to connect do not have overlapping values.
The default HVN CIDR block value does not overlap with the default CIDR block value for AWS VPCs (172.31.0.0/16). However, if you are planning to use this HVN in production, we recommend adding a custom value instead of using the default.
Should it be update to include/mention Azure VNets or make the verbiage a bit more generic like "your cloud provider network" or something of the sort so it covers, AWS, Azure and future cloud providers too?
New or Affected Resource(s)
Community Note
The text was updated successfully, but these errors were encountered: