Azure Service Fabric Managed Clusters Service Fabric Managed Cluster

This page shows how to write Terraform and Azure Resource Manager for Service Fabric Managed Clusters Service Fabric Managed Cluster and write them securely.

azurerm_service_fabric_managed_cluster (Terraform)

The Service Fabric Managed Cluster in Service Fabric Managed Clusters can be configured in Terraform with the resource name azurerm_service_fabric_managed_cluster. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Review your Terraform file for Azure best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).

Parameters

The following arguments are supported:

  • client_connection_port - (Required) Port to use when connecting to the cluster.

  • http_gateway_port - (Required) Port that should be used by the Service Fabric Explorer to visualize applications and cluster status.

  • lb_rule - (Required) One or more lb_rule blocks as defined below.

  • location - (Required) The Azure Region where the Resource Group should exist. Changing this forces a new Resource Group to be created.

  • name - (Required) The name which should be used for this Resource Group. Changing this forces a new Resource Group to be created.

  • resource_group_name - (Required) The name of the Resource Group where the Resource Group should exist.


  • authentication - (Optional) Controls how connections to the cluster are authenticated. A authentication block as defined below.

  • backup_service_enabled - (Optional) If true, backup service is enabled.

  • custom_fabric_setting - (Optional) One or more custom_fabric_setting blocks as defined below.

  • dns_name - (Optional) Hostname for the cluster. If unset the cluster's name will be used..

  • dns_service_enabled - (Optional) If true, DNS service is enabled.

  • node_type - (Optional) One or more node_type blocks as defined below.

  • password - (Optional) Administrator password for the VMs that will be created as part of this cluster.

  • sku - (Optional) SKU for this cluster. Changing this forces a new resource to be created. Default is Basic, allowed values are either Basic or Standard.

  • tags - (Optional) A mapping of tags which should be assigned to the Resource Group.

  • upgrade_wave - (Optional) Upgrade wave for the fabric runtime. Default is Wave0, allowed value must be one of Wave0, Wave1, or Wave2.

  • username - (Optional) Administrator password for the VMs that will be created as part of this cluster.


A active_directory block supports the following:

  • client_application_id - (Required) The ID of the Client Application.

  • cluster_application_id - (Required) The ID of the Cluster Application.

  • tenant_id - (Required) The ID of the Tenant.


A authentication block supports the following:

  • active_directory - (Optional) A active_directory block as defined above.

  • certificate - (Optional) One or more certificate blocks as defined below.


A certificate block supports the following:

  • thumbprint - (Required) The thumbprint of the certificate.

  • type - (Required) The type of the certificate. Can be AdminClient or ReadOnlyClient.

  • common_name - (Optional) The certificate's CN.


A certificates block supports the following:

  • store - (Required) The certificate store on the Virtual Machine to which the certificate should be added.

  • url - (Required) The URL of a certificate that has been uploaded to Key Vault as a secret


A custom_fabric_setting block supports the following:

  • parameter - (Required) Parameter name.

  • section - (Required) Section name.

  • value - (Required) Parameter value.


A lb_rule block supports the following:

  • backend_port - (Required) LB Backend port.

  • frontend_port - (Required) LB Frontend port.

  • probe_protocol - (Required) Protocol for the probe. Can be one of tcp, udp, http, or https.

  • probe_request_path - (Required) Path for the probe to check, when probe protocol is set to http.

  • protocol - (Required) The transport protocol used in this rule. Can be one of tcp or udp.


A node_type block supports the following:

  • application_port_range - (Required) Sets the port range available for applications. Format is <from_port>-<to_port>, for example 10000-20000.

  • data_disk_size_gb - (Required) The size of the data disk in gigabytes..

  • ephemeral_port_range - (Required) Sets the port range available for the OS. Format is <from_port>-<to_port>, for example 10000-20000. There has to be at least 255 ports available and cannot overlap with application_port_range..

  • name - (Required) The name which should be used for this node type.

  • vm_image_offer - (Required) The offer type of the marketplace image cluster VMs will use.

  • vm_image_publisher - (Required) The publisher of the marketplace image cluster VMs will use.

  • vm_image_sku - (Required) The SKU of the marketplace image cluster VMs will use.

  • vm_image_version - (Required) The version of the marketplace image cluster VMs will use.

  • vm_instance_count - (Required) The number of instances this node type will launch.

  • vm_size - (Required) The size of the instances in this node type.

  • capacities - (Optional) Specifies a list of key/value pairs used to set capacity tags for this node type.

  • data_disk_type - (Optional) The type of the disk to use for storing data. It can be one of Premium_LRS, Standard_LRS, or StandardSSD_LRS.

  • multiple_placement_groups_enabled - (Optional) If set the node type can be composed of multiple placement groups.

  • placement_properties - (Optional) Specifies a list of placement tags that can be used to indicate where services should run..

  • primary - (Optional) If set to true, system services will run on this node type. Only one node type should be marked as primary. Primary node type cannot be deleted or changed once they're created.

  • stateless - (Optional) If set to true, only stateless workloads can run on this node type.

  • vm_secrets - (Optional) One or more vm_secrets blocks as defined below.


A vm_secrets block supports the following:

  • certificates - (Required) One or more certificates blocks as defined above.

  • vault_id - (Required) The ID of the Vault that contain the certificates.

In addition to the Arguments listed above - the following Attributes are exported:

  • id - The ID of the Resource Group.

Explanation in Terraform Registry

Manages a Resource Group.

Microsoft.ServiceFabric/managedClusters (Azure Resource Manager)

The managedClusters in Microsoft.ServiceFabric can be configured in Azure Resource Manager with the resource name Microsoft.ServiceFabric/managedClusters. The following sections describe how to use the resource and its parameters.

Example Usage from GitHub

An example could not be found in GitHub.

Frequently asked questions

What is Azure Service Fabric Managed Clusters Service Fabric Managed Cluster?

Azure Service Fabric Managed Clusters Service Fabric Managed Cluster is a resource for Service Fabric Managed Clusters of Microsoft Azure. Settings can be wrote in Terraform.