Skip to content

Latest commit

 

History

History
509 lines (281 loc) · 24.9 KB

kubernetes_cluster.html.markdown

File metadata and controls

509 lines (281 loc) · 24.9 KB
subcategory layout page_title description
Container
azurerm
Azure Resource Manager: azurerm_kubernetes_cluster
Manages a managed Kubernetes Cluster (also known as AKS / Azure Kubernetes Service)

azurerm_kubernetes_cluster

Manages a Managed Kubernetes Cluster (also known as AKS / Azure Kubernetes Service)

~> Note: All arguments including the client secret will be stored in the raw state as plain-text. Read more about sensitive data in state.

Example Usage

This example provisions a basic Managed Kubernetes Cluster. Other examples of the azurerm_kubernetes_cluster resource can be found in the ./examples/kubernetes directory within the Github Repository

resource "azurerm_resource_group" "example" {
  name     = "example-resources"
  location = "West Europe"
}

resource "azurerm_kubernetes_cluster" "example" {
  name                = "example-aks1"
  location            = azurerm_resource_group.example.location
  resource_group_name = azurerm_resource_group.example.name
  dns_prefix          = "exampleaks1"

  default_node_pool {
    name       = "default"
    node_count = 1
    vm_size    = "Standard_D2_v2"
  }

  identity {
    type = "SystemAssigned"
  }

  tags = {
    Environment = "Production"
  }
}

output "client_certificate" {
  value = azurerm_kubernetes_cluster.example.kube_config.0.client_certificate
}

output "kube_config" {
  value = azurerm_kubernetes_cluster.example.kube_config_raw
}

Argument Reference

The following arguments are supported:

  • name - (Required) The name of the Managed Kubernetes Cluster to create. Changing this forces a new resource to be created.

  • location - (Required) The location where the Managed Kubernetes Cluster should be created. Changing this forces a new resource to be created.

  • resource_group_name - (Required) Specifies the Resource Group where the Managed Kubernetes Cluster should exist. Changing this forces a new resource to be created.

  • default_node_pool - (Required) A default_node_pool block as defined below.

  • dns_prefix - (Required) DNS prefix specified when creating the managed cluster. Changing this forces a new resource to be created.

-> NOTE: The dns_prefix must contain between 3 and 45 characters, and can contain only letters, numbers, and hyphens. It must start with a letter and must end with a letter or a number.

In addition, one of either identity or service_principal blocks must be specified.


  • addon_profile - (Optional) A addon_profile block as defined below.

  • api_server_authorized_ip_ranges - (Optional) The IP ranges to whitelist for incoming traffic to the masters.

  • auto_scaler_profile - (Optional) A auto_scaler_profile block as defined below.

  • disk_encryption_set_id - (Optional) The ID of the Disk Encryption Set which should be used for the Nodes and Volumes. More information can be found in the documentation.

  • identity - (Optional) An identity block as defined below. Changing this forces a new resource to be created.

-> NOTE: One of either identity or service_principal must be specified.

  • kubernetes_version - (Optional) Version of Kubernetes specified when creating the AKS managed cluster. If not specified, the latest recommended version will be used at provisioning time (but won't auto-upgrade).

-> NOTE: Upgrading your cluster may take up to 10 minutes per node.

  • linux_profile - (Optional) A linux_profile block as defined below.

  • network_profile - (Optional) A network_profile block as defined below.

-> NOTE: If network_profile is not defined, kubenet profile will be used by default.

  • node_resource_group - (Optional) The name of the Resource Group where the Kubernetes Nodes should exist. Changing this forces a new resource to be created.

-> NOTE: Azure requires that a new, non-existent Resource Group is used, as otherwise the provisioning of the Kubernetes Service will fail.

  • private_cluster_enabled Should this Kubernetes Cluster have its API server only exposed on internal IP addresses? This provides a Private IP Address for the Kubernetes API on the Virtual Network where the Kubernetes Cluster is located. Defaults to false. Changing this forces a new resource to be created.

  • role_based_access_control - (Optional) A role_based_access_control block. Changing this forces a new resource to be created.

  • service_principal - (Optional) A service_principal block as documented below.

-> NOTE: One of either identity or service_principal must be specified.

  • sku_tier - (Optional) The SKU Tier that should be used for this Kubernetes Cluster. Possible values are Free and Paid (which includes the Uptime SLA). Defaults to Free.

~> Note: It is currently possible to upgrade in place from Free to Paid. However, changing this value from Paid to Free will force a new resource to be created.

  • tags - (Optional) A mapping of tags to assign to the resource.

  • windows_profile - (Optional) A windows_profile block as defined below.


A aci_connector_linux block supports the following:

  • enabled - (Required) Is the virtual node addon enabled?

  • subnet_name - (Optional) The subnet name for the virtual nodes to run. This is required when aci_connector_linux enabled argument is set to true.

-> NOTE: AKS will add a delegation to the subnet named here. To prevent further runs from failing you should make sure that the subnet you create for virtual nodes has a delegation, like so.

resource "azurerm_subnet" "virtual" {

  #...

  delegation {
    name = "aciDelegation"
    service_delegation {
      name    = "Microsoft.ContainerInstance/containerGroups"
      actions = ["Microsoft.Network/virtualNetworks/subnets/action"]
    }
  }
}

A addon_profile block supports the following:

-> NOTE: At this time ACI Connector's are not supported in Azure China.

-> NOTE: At this time Azure Policy is not supported in Azure China or Azure US Government.

~> Note: Azure Policy is in Public Preview - more information and details on how to opt into the Preview can be found in this article.

  • http_application_routing - (Optional) A http_application_routing block as defined below.

-> NOTE: At this time HTTP Application Routing is not supported in Azure China or Azure US Government.


A auto_scaler_profile block supports the following:

  • balance_similar_node_groups - Detect similar node groups and balance the number of nodes between them. Defaults to false.

  • max_graceful_termination_sec - Maximum number of seconds the cluster autoscaler waits for pod termination when trying to scale down a node. Defaults to 600.

  • new_pod_scale_up_delay - For scenarios like burst/batch scale where you don't want CA to act before the kubernetes scheduler could schedule all the pods, you can tell CA to ignore unscheduled pods before they're a certain age. Defaults to 10s.

  • scale_down_delay_after_add - How long after the scale up of AKS nodes the scale down evaluation resumes. Defaults to 10m.

  • scale_down_delay_after_delete - How long after node deletion that scale down evaluation resumes. Defaults to the value used for scan_interval.

  • scale_down_delay_after_failure - How long after scale down failure that scale down evaluation resumes. Defaults to 3m.

  • scan_interval - How often the AKS Cluster should be re-evaluated for scale up/down. Defaults to 10s.

  • scale_down_unneeded - How long a node should be unneeded before it is eligible for scale down. Defaults to 10m.

  • scale_down_unready - How long an unready node should be unneeded before it is eligible for scale down. Defaults to 20m.

  • scale_down_utilization_threshold - Node utilization level, defined as sum of requested resources divided by capacity, below which a node can be considered for scale down. Defaults to 0.5.


A azure_active_directory block supports the following:

  • managed - Is the Azure Active Directory integration Managed, meaning that Azure will create/manage the Service Principal used for integration.

  • tenant_id - (Optional) The Tenant ID used for Azure Active Directory Application. If this isn't specified the Tenant ID of the current Subscription is used.

When managed is set to true the following properties can be specified:

  • admin_group_object_ids - (Optional) A list of Object IDs of Azure Active Directory Groups which should have Admin Role on the Cluster.

When managed is set to false the following properties can be specified:

  • client_app_id - (Required) The Client ID of an Azure Active Directory Application.

  • server_app_id - (Required) The Server ID of an Azure Active Directory Application.

  • server_app_secret - (Required) The Server Secret of an Azure Active Directory Application.


A azure_policy block supports the following:

  • enabled - (Required) Is the Azure Policy for Kubernetes Add On enabled?

A default_node_pool block supports the following:

  • name - (Required) The name which should be used for the default Kubernetes Node Pool. Changing this forces a new resource to be created.

  • vm_size - (Required) The size of the Virtual Machine, such as Standard_DS2_v2.

  • availability_zones - (Optional) A list of Availability Zones across which the Node Pool should be spread. Changing this forces a new resource to be created.

-> NOTE: This requires that the type is set to VirtualMachineScaleSets and that load_balancer_sku is set to Standard.

-> NOTE: This requires that the type is set to VirtualMachineScaleSets.

-> NOTE: If you're using AutoScaling, you may wish to use Terraform's ignore_changes functionality to ignore changes to the node_count field.

  • enable_host_encryption - (Optional) Should the nodes in the Default Node Pool have host encryption enabled? Defaults to false.

  • enable_node_public_ip - (Optional) Should nodes in this Node Pool have a Public IP Address? Defaults to false.

  • max_pods - (Optional) The maximum number of pods that can run on each agent. Changing this forces a new resource to be created.

  • node_labels - (Optional) A map of Kubernetes labels which should be applied to nodes in the Default Node Pool. Changing this forces a new resource to be created.

  • orchestrator_version - (Optional) Version of Kubernetes used for the Agents. If not specified, the latest recommended version will be used at provisioning time (but won't auto-upgrade)

-> Note: This version must be supported by the Kubernetes Cluster - as such the version of Kubernetes used on the Cluster/Control Plane may need to be upgraded first.

  • os_disk_size_gb - (Optional) The size of the OS Disk which should be used for each agent in the Node Pool. Changing this forces a new resource to be created.

  • os_disk_type - (Optional) The type of disk which should be used for the Operating System. Possible values are Ephemeral and Managed. Defaults to Managed. Changing this forces a new resource to be created.

  • type - (Optional) The type of Node Pool which should be created. Possible values are AvailabilitySet and VirtualMachineScaleSets. Defaults to VirtualMachineScaleSets.

  • tags - (Optional) A mapping of tags to assign to the Node Pool.

~> At this time there's a bug in the AKS API where Tags for a Node Pool are not stored in the correct case - you may wish to use Terraform's ignore_changes functionality to ignore changes to the casing until this is fixed in the AKS API.

  • vnet_subnet_id - (Optional) The ID of a Subnet where the Kubernetes Node Pool should exist. Changing this forces a new resource to be created.

~> NOTE: A Route Table must be configured on this Subnet.

If enable_auto_scaling is set to true, then the following fields can also be configured:

  • max_count - (Required) The maximum number of nodes which should exist in this Node Pool. If specified this must be between 1 and 1000.

  • min_count - (Required) The minimum number of nodes which should exist in this Node Pool. If specified this must be between 1 and 1000.

  • node_count - (Optional) The initial number of nodes which should exist in this Node Pool. If specified this must be between 1 and 1000 and between min_count and max_count.

-> NOTE: If specified you may wish to use Terraform's ignore_changes functionality to ignore changes to this field.

If enable_auto_scaling is set to false, then the following fields can also be configured:

  • node_count - (Required) The number of nodes which should exist in this Node Pool. If specified this must be between 1 and 1000.

-> NOTE: If enable_auto_scaling is set to false both min_count and max_count fields need to be set to null or omitted from the configuration.


A http_application_routing block supports the following:

  • enabled (Required) Is HTTP Application Routing Enabled?

An identity block supports the following:

  • type - The type of identity used for the managed cluster. Possible values are SystemAssigned and UserAssigned. If UserAssigned is set, a user_assigned_identity_id must be set as well.
  • user_assigned_identity_id - (Optional) The ID of a user assigned identity.

A kube_dashboard block supports the following:

  • enabled - (Required) Is the Kubernetes Dashboard enabled?

A linux_profile block supports the following:

  • admin_username - (Required) The Admin Username for the Cluster. Changing this forces a new resource to be created.

  • ssh_key - (Required) An ssh_key block. Only one is currently allowed. Changing this forces a new resource to be created.


A network_profile block supports the following:

  • network_plugin - (Required) Network plugin to use for networking. Currently supported values are azure and kubenet. Changing this forces a new resource to be created.

-> NOTE: When network_plugin is set to azure - the vnet_subnet_id field in the default_node_pool block must be set and pod_cidr must not be set.

  • network_mode - (Optional) Network mode to be used with Azure CNI. Possible values are bridge or transparent. Changing this forces a new resource to be created.

~> NOTE: This property can only be set when network_plugin is set to azure.

-> NOTE: network_mode Is currently in Preview on an opt-in basis. To use it, enable feature AKSNetworkModePreview for namespace Microsoft.ContainerService.

~> NOTE: When network_policy is set to azure, the network_plugin field can only be set to azure.

  • dns_service_ip - (Optional) IP address within the Kubernetes service address range that will be used by cluster service discovery (kube-dns). Changing this forces a new resource to be created.

  • docker_bridge_cidr - (Optional) IP address (in CIDR notation) used as the Docker bridge IP address on nodes. Changing this forces a new resource to be created.

  • outbound_type - (Optional) The outbound (egress) routing method which should be used for this Kubernetes Cluster. Possible values are loadBalancer and userDefinedRouting. Defaults to loadBalancer.

  • pod_cidr - (Optional) The CIDR to use for pod IP addresses. This field can only be set when network_plugin is set to kubenet. Changing this forces a new resource to be created.

  • service_cidr - (Optional) The Network Range used by the Kubernetes service. Changing this forces a new resource to be created.

~> NOTE: This range should not be used by any network element on or connected to this VNet. Service address CIDR must be smaller than /12. docker_bridge_cidr, dns_service_ip and service_cidr should all be empty or all should be set.

Examples of how to use AKS with Advanced Networking can be found in the ./examples/kubernetes/ directory in the Github repository.

  • load_balancer_sku - (Optional) Specifies the SKU of the Load Balancer used for this Kubernetes Cluster. Possible values are Basic and Standard. Defaults to Standard.

  • load_balancer_profile - (Optional) A load_balancer_profile block. This can only be specified when load_balancer_sku is set to Standard.


A load_balancer_profile block supports the following:

~> NOTE: These options are mutually exclusive. Note that when specifying outbound_ip_address_ids (azurerm_public_ip) the SKU must be Standard.

  • outbound_ports_allocated - (Optional) Number of desired SNAT port for each VM in the clusters load balancer. Must be between 0 and 64000 inclusive. Defaults to 0.

  • idle_timeout_in_minutes - (Optional) Desired outbound flow idle timeout in minutes for the cluster load balancer. Must be between 4 and 120 inclusive. Defaults to 30.

  • managed_outbound_ip_count - (Optional) Count of desired managed outbound IPs for the cluster load balancer. Must be between 1 and 100 inclusive.

-> NOTE User has to explicitly set managed_outbound_ip_count to empty slice ([]) to remove it.

  • outbound_ip_prefix_ids - (Optional) The ID of the outbound Public IP Address Prefixes which should be used for the cluster load balancer.

-> NOTE User has to explicitly set outbound_ip_prefix_ids to empty slice ([]) to remove it.

  • outbound_ip_address_ids - (Optional) The ID of the Public IP Addresses which should be used for outbound communication for the cluster load balancer.

-> NOTE User has to explicitly set outbound_ip_address_ids to empty slice ([]) to remove it.


A oms_agent block supports the following:

  • enabled - (Required) Is the OMS Agent Enabled?

  • log_analytics_workspace_id - (Optional) The ID of the Log Analytics Workspace which the OMS Agent should send data to. Must be present if enabled is true.

  • oms_agent_identity - An oms_agent_identity block as defined below.


A role_based_access_control block supports the following:

  • azure_active_directory - (Optional) An azure_active_directory block.

  • enabled - (Required) Is Role Based Access Control Enabled? Changing this forces a new resource to be created.


A service_principal block supports the following:

  • client_id - (Required) The Client ID for the Service Principal.

  • client_secret - (Required) The Client Secret for the Service Principal.


A ssh_key block supports the following:

  • key_data - (Required) The Public SSH Key used to access the cluster. Changing this forces a new resource to be created.

A windows_profile block supports the following:

  • admin_username - (Required) The Admin Username for Windows VMs.

  • admin_password - (Required) The Admin Password for Windows VMs.

Attributes Reference

The following attributes are exported:

  • id - The Kubernetes Managed Cluster ID.

  • fqdn - The FQDN of the Azure Kubernetes Managed Cluster.

  • private_fqdn - The FQDN for the Kubernetes Cluster when private link has been enabled, which is only resolvable inside the Virtual Network used by the Kubernetes Cluster.

  • kube_admin_config - A kube_admin_config block as defined below. This is only available when Role Based Access Control with Azure Active Directory is enabled.

  • kube_admin_config_raw - Raw Kubernetes config for the admin account to be used by kubectl and other compatible tools. This is only available when Role Based Access Control with Azure Active Directory is enabled.

  • kube_config - A kube_config block as defined below.

  • kube_config_raw - Raw Kubernetes config to be used by kubectl and other compatible tools

  • http_application_routing - A http_application_routing block as defined below.

  • node_resource_group - The auto-generated Resource Group which contains the resources for this Managed Kubernetes Cluster.

  • kubelet_identity - A kubelet_identity block as defined below.


A http_application_routing block exports the following:

  • http_application_routing_zone_name - The Zone Name of the HTTP Application Routing.

A load_balancer_profile block exports the following:

  • effective_outbound_ips - The outcome (resource IDs) of the specified arguments.

The identity block exports the following:

  • principal_id - The principal id of the system assigned identity which is used by master components.

  • tenant_id - The tenant id of the system assigned identity which is used by master components.


The kubelet_identity block exports the following:

  • client_id - The Client ID of the user-defined Managed Identity assigned to the Kubelets.

  • object_id - The Object ID of the user-defined Managed Identity assigned to the Kubelets.

  • user_assigned_identity_id - The ID of the User Assigned Identity assigned to the Kubelets.


The oms_agent_identity block exports the following:

  • client_id - The Client ID of the user-defined Managed Identity used by the OMS Agents.

  • object_id - The Object ID of the user-defined Managed Identity used by the OMS Agents.

  • user_assigned_identity_id - The ID of the User Assigned Identity used by the OMS Agents.


The kube_admin_config and kube_config blocks export the following:

  • client_key - Base64 encoded private key used by clients to authenticate to the Kubernetes cluster.

  • client_certificate - Base64 encoded public certificate used by clients to authenticate to the Kubernetes cluster.

  • cluster_ca_certificate - Base64 encoded public CA certificate used as the root of trust for the Kubernetes cluster.

  • host - The Kubernetes cluster server host.

  • username - A username used to authenticate to the Kubernetes cluster.

  • password - A password or token used to authenticate to the Kubernetes cluster.

-> NOTE: It's possible to use these credentials with the Kubernetes Provider like so:

provider "kubernetes" {
  load_config_file       = "false"
  host                   = azurerm_kubernetes_cluster.main.kube_config.0.host
  username               = azurerm_kubernetes_cluster.main.kube_config.0.username
  password               = azurerm_kubernetes_cluster.main.kube_config.0.password
  client_certificate     = "${base64decode(azurerm_kubernetes_cluster.main.kube_config.0.client_certificate)}"
  client_key             = "${base64decode(azurerm_kubernetes_cluster.main.kube_config.0.client_key)}"
  cluster_ca_certificate = "${base64decode(azurerm_kubernetes_cluster.main.kube_config.0.cluster_ca_certificate)}"
}

Timeouts

The timeouts block allows you to specify timeouts for certain actions:

  • create - (Defaults to 90 minutes) Used when creating the Kubernetes Cluster.
  • update - (Defaults to 90 minutes) Used when updating the Kubernetes Cluster.
  • read - (Defaults to 5 minutes) Used when retrieving the Kubernetes Cluster.
  • delete - (Defaults to 90 minutes) Used when deleting the Kubernetes Cluster.

Import

Managed Kubernetes Clusters can be imported using the resource id, e.g.

terraform import azurerm_kubernetes_cluster.cluster1 /subscriptions/00000000-0000-0000-0000-000000000000/resourcegroups/group1/providers/Microsoft.ContainerService/managedClusters/cluster1