»HashiCorp Virtual Network (HVN) Routes
The HVN Route provides a networking abstraction for enabling network traffic between the HVN and a target HVN Connection.
When an HVN Route is created, it is added to the route table of the HVN, enabling HCP resources to communicate with your provider resources.
An HVN Route does two things.
- Directs network traffic from the HVN to the target.
- Enables communication between the destination and all existing clusters (including clusters created in the future) within the HVN. Allowed ports depend on the type of the cluster.
An HVN Route is composed of two parts, a destination and a target for the network traffic.
- The destination is specified by the CIDR block of the resource you want to reach via your target.
- A target represents an HVN Connection where traffic is to be routed,
such as a Peering Connection or an AWS Transit Gateway. When creating an HVN
Targetdrop-down will list known targets for selection.
»CIDR Block Requirements
An HVN Route will allow any CIDR block that does not overlap with the parent HVN. Overlapping CIDRs between different HVN Routes are allowed, but the HVN Route with the most specific CIDR will take priority when routing network traffic to an IP address that falls into CIDRs of multiple HVN Routes. HVN Routes cannot be more specific than an existing route whose target is an HVN-HVN Peering connection as they enable additional platform features.