From 6c4fcbfb79139c3cd2562c7c454d70838d2271b2 Mon Sep 17 00:00:00 2001 From: Dane Harrigan Date: Tue, 28 Jun 2022 10:55:03 -0400 Subject: [PATCH 1/2] Refactor hcp_hvn cloud provider documentation to be more generic Co-authored-by: Dominic Gregoire --- templates/resources/hvn.md.tmpl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/templates/resources/hvn.md.tmpl b/templates/resources/hvn.md.tmpl index 4878bf228..6a8ea62a8 100644 --- a/templates/resources/hvn.md.tmpl +++ b/templates/resources/hvn.md.tmpl @@ -17,9 +17,9 @@ We recommend the following when selecting the CIDR block of an HVN: - The CIDR block value must end between /16 and /25. -- 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. +- If the CIDR block values for your HCP HVN and your cloud provider’s virtual network overlap you will not be able to establish a connection. The following are default CIDR block values to be aware of: HCP HVN (172.25.16.0/20), AWS VPC (172.31.0.0/16), and Azure VNet (172.29.0.0/24). Avoid creating overlapping networks. -- 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. +- If you’re creating a HVN for use in production it's recommended that you specify a CIDR block value that does not overlap with the other HVNs already created in your organization. You will not be able to connect two HVNs with overlapping CIDR block values. ## Example Usage From 7c9adda01f639489b67cc41ebf5d79b9a60c29ed Mon Sep 17 00:00:00 2001 From: Dane Harrigan Date: Tue, 28 Jun 2022 11:00:07 -0400 Subject: [PATCH 2/2] Regenerate documentation Co-authored-by: Dominic Gregoire --- docs/resources/hvn.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/resources/hvn.md b/docs/resources/hvn.md index 44eaa7019..25ea29af7 100644 --- a/docs/resources/hvn.md +++ b/docs/resources/hvn.md @@ -17,9 +17,9 @@ We recommend the following when selecting the CIDR block of an HVN: - The CIDR block value must end between /16 and /25. -- 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. +- If the CIDR block values for your HCP HVN and your cloud provider’s virtual network overlap you will not be able to establish a connection. The following are default CIDR block values to be aware of: HCP HVN (172.25.16.0/20), AWS VPC (172.31.0.0/16), and Azure VNet (172.29.0.0/24). Avoid creating overlapping networks. -- 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. +- If you’re creating a HVN for use in production it's recommended that you specify a CIDR block value that does not overlap with the other HVNs already created in your organization. You will not be able to connect two HVNs with overlapping CIDR block values. ## Example Usage