| Name | Version |
|---|---|
| azurerm | >=3.87.0 |
| azurerm.peer | >=3.87.0 |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| alias_subs_id | Alias for remote provider in module. | string |
"" |
no |
| allow_forwarded_traffic_vnet1 | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
| allow_forwarded_traffic_vnet2 | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
| allow_forwarded_traffic_vnet_diff_subs | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
| allow_gateway_transit_vnet1 | Controls gatewayLinks can be used in the remote virtual network’s link to the local virtual network. | bool |
false |
no |
| allow_gateway_transit_vnet2 | Controls gatewayLinks can be used in the remote virtual network’s link to the local virtual network. | bool |
false |
no |
| allow_gateway_transit_vnet_diff_subs | Controls gatewayLinks can be used in the different subscription virtual network’s link to the local virtual network. | bool |
false |
no |
| allow_virtual_network_access | Controls if the VMs in the remote virtual network can access VMs in the local virtual network. | bool |
true |
no |
| diff_subs_resource_group_name | The name of remote resource group to be imported. | string |
"" |
no |
| different_rg | Flag to tell whether peering is to be done in same in resource group or different resource group | bool |
false |
no |
| enabled_diff_subs_peering | n/a | bool |
false |
no |
| enabled_peering | Set to false to prevent the module from creating any resources. | bool |
false |
no |
| resource_group_1_name | The name of 1st existing resource group to be imported. | string |
"" |
no |
| resource_group_2_name | The name of 2nd existing resource group to be imported. | string |
"" |
no |
| use_remote_gateways_vnet1 | Controls if remote gateways can be used on the local virtual network | bool |
false |
no |
| use_remote_gateways_vnet2 | Controls if remote gateways can be used on the local virtual network | bool |
false |
no |
| use_remote_gateways_vnet_diff_subs | Controls if remote gateways can be used on the different subscription virtual network | bool |
false |
no |
| vnet_1_id | The full Azure resource ID of the remote virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
| vnet_1_name | The name of the virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
| vnet_2_id | The full Azure resource ID of the remote virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
| vnet_2_name | The name of the remote virtual network. | string |
"" |
no |
| vnet_diff_subs_id | The id of the remote virtual network. | string |
"" |
no |
| vnet_diff_subs_name | The name of the remote virtual network. | string |
"" |
no |
| Name | Type |
|---|---|
| azurerm_virtual_network_peering.peering | resource |
| azurerm_virtual_network_peering.peering_back | resource |
| azurerm_virtual_network_peering.peering_back_diff_subs | resource |
| Name | Description |
|---|---|
| vnet_peer_1_id | The id of the newly created virtual network peering in on first virtual netowork. |
| vnet_peer_1_name | The name of the newly created virtual network peering in on first virtual netowork. |
| vnet_peer_2_id | The id of the newly created virtual network peering in on second virtual netowork. |
| vnet_peer_2_name | The name of the newly created virtual network peering in on second virtual netowork. |
| vnet_peer_diff_subs_id | The id of the newly created virtual network peering in on different subscription virtual netowork. |
| vnet_peer_diff_subs_name | The name of the newly created virtual network peering in on different subscription virtual netowork. |
Since 2016 opsZero has been providing Kubernetes expertise to companies of all sizes on any Cloud. With a focus on AI and Compliance we can say we seen it all whether SOC2, HIPAA, PCI-DSS, ITAR, FedRAMP, CMMC we have you and your customers covered.
We provide support to organizations in the following ways:
- Modernize or Migrate to Kubernetes
- Cloud Infrastructure with Kubernetes on AWS, Azure, Google Cloud, or Bare Metal
- Building AI and Data Pipelines on Kubernetes
- Optimizing Existing Kubernetes Workloads
We do this with a high-touch support model where you:
- Get access to us on Slack, Microsoft Teams or Email
- Get 24/7 coverage of your infrastructure
- Get an accelerated migration to Kubernetes
Please schedule a call if you need support.
