Hci
Manages an Azure Stack HCI Logical Network.
Example Usage
resources:
example:
type: azure:core:ResourceGroup
properties:
name: example-rg
location: West Europe
exampleHciLogicalNetwork:
type: azure:stack:HciLogicalNetwork
name: example
properties:
name: example-hci-ln
resourceGroupName: ${example.name}
location: ${example.location}
customLocationId: /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/rg1/providers/Microsoft.ExtendedLocation/customLocations/cl1
virtualSwitchName: ConvergedSwitch(managementcompute)
dnsServers:
- 10.0.0.7
- 10.0.0.8
subnet:
ipAllocationMethod: Static
addressPrefix: 10.0.0.0/24
vlanId: 123
route:
addressPrefix: 0.0.0.0/0
nextHopIpAddress: 10.0.0.1
tags:
foo: barAPI Providers
This resource uses the following Azure API Providers:
Microsoft.AzureStackHCI: 2024-01-01
Import
Azure Stack HCI Logical Networks can be imported using the resource id, e.g.
$ pulumi import azure:stack/hciLogicalNetwork:HciLogicalNetwork example /subscriptions/00000000-0000-0000-0000-000000000000/resourceGroups/group1/providers/Microsoft.AzureStackHCI/logicalNetworks/ln1Properties
The ID of Custom Location where the Azure Stack HCI Logical Network should exist. Changing this forces a new resource to be created.
A list of IPv4 addresses of DNS servers available to VMs deployed in the Logical Networks. Changing this forces a new resource to be created.
The name of the Resource Group where the Azure Stack HCI Logical Network should exist. Changing this forces a new resource to be created.
A subnet block as defined below. Changing this forces a new resource to be created.
The name of the virtual switch on the cluster used to associate with the Azure Stack HCI Logical Network. Possible switch names can be retrieved by following this Azure guide. Changing this forces a new resource to be created.