ManagedClusterHostedSystemProfile Constructors
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.
Overloads
| Name | Description |
|---|---|
| ManagedClusterHostedSystemProfile() |
Initializes a new instance of the ManagedClusterHostedSystemProfile class. |
| ManagedClusterHostedSystemProfile(Nullable<Boolean>, String, String) |
Initializes a new instance of the ManagedClusterHostedSystemProfile class. |
ManagedClusterHostedSystemProfile()
Initializes a new instance of the ManagedClusterHostedSystemProfile class.
public ManagedClusterHostedSystemProfile();
Public Sub New ()
Applies to
ManagedClusterHostedSystemProfile(Nullable<Boolean>, String, String)
Initializes a new instance of the ManagedClusterHostedSystemProfile class.
public ManagedClusterHostedSystemProfile(bool? enabled = default, string systemNodeSubnetId = default, string nodeSubnetId = default);
new Microsoft.Azure.Management.ContainerService.Models.ManagedClusterHostedSystemProfile : Nullable<bool> * string * string -> Microsoft.Azure.Management.ContainerService.Models.ManagedClusterHostedSystemProfile
Public Sub New (Optional enabled As Nullable(Of Boolean) = Nothing, Optional systemNodeSubnetId As String = Nothing, Optional nodeSubnetId As String = Nothing)
Parameters
- systemNodeSubnetId
- String
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
- String
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.