ArmContainerServiceModelFactory.ManagedClusterHostedSystemProfile Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
public static Azure.ResourceManager.ContainerService.Models.ManagedClusterHostedSystemProfile ManagedClusterHostedSystemProfile(bool? isHostedSystemAddonsEnabled = default, Azure.Core.ResourceIdentifier systemNodeSubnetId = default, Azure.Core.ResourceIdentifier nodeSubnetId = default);static member ManagedClusterHostedSystemProfile : Nullable<bool> * Azure.Core.ResourceIdentifier * Azure.Core.ResourceIdentifier -> Azure.ResourceManager.ContainerService.Models.ManagedClusterHostedSystemProfilePublic Shared Function ManagedClusterHostedSystemProfile (Optional isHostedSystemAddonsEnabled As Nullable(Of Boolean) = Nothing, Optional systemNodeSubnetId As ResourceIdentifier = Nothing, Optional nodeSubnetId As ResourceIdentifier = Nothing) As ManagedClusterHostedSystemProfileParameters
Whether to enable hosted system addons for the cluster.
- systemNodeSubnetId
- ResourceIdentifier
The ID of the subnet that will be joined by system nodes managed and hosted by AKS for running critical system addons. This ID must be provided together with nodeSubnetID and apiserverAccessProfile.subnetId, and all three subnet IDs must belong to the same VNet. If you don’t specify it, AKS will create a subnet in the managed resource group using a default /26 CIDR.
- nodeSubnetId
- ResourceIdentifier
The ID of the subnet that will be joined by worker nodes managed by node auto provisioner for running workload pods in your tenant. This must be provided together with systemNodeSubnetID and apiserverAccessProfile.subnetId, and all three subnet IDs must be in the same VNet. If you don’t specify it, AKS will create a subnet in the managed resource group using a default /16 CIDR.
Returns
A new ManagedClusterHostedSystemProfile instance for mocking.
