Instance Type and Quantity

« list of all parameters

Applicable for:
ProviderAWS, Azure, GCP, VMware vSphere, On-Premises
TAB - SectionINSTANCES - Master Configuration, Instance Group(s)

Overview

The Instance Type parameter along with the Masters (for master node section) or Nodes (for work node groups) distinguishes between the type and number of nodes that are supposed to work as master or work in your cluster (separately for each group).

Before setting, see Kublr minimum hardware recommendations.

For AWS

Recommended configurations:

  • 1 / t2.medium for development / staging environment clusters
  • 3 / t2.medium for staging / low traffic production environments
  • 3 / m4.large for robust large production environments

See details here.

For Azure

Recommended configurations:

  • 1 / Standard_D2_v2 for development / staging environment clusters
  • 3 / Standard_A2_v2 for staging / low traffic production environments
  • 3 / Standard_D3_v2 for robust large production environments

See details here.

For GCP

Recommended configurations:

  • 1 / n1-standard-2 for development / staging environment clusters
  • 3 / n1-standard-2 for staging / low traffic production environments
  • 3 / n1-standard-2 for robust large production environments

See details here.

For VMware vSphere

For VMware vSphere, intead of the Instance Type parameter, the following parameters are used for VM (node) initialization:

  • VM Template Kublr Supports different initialization schemes provided by vSphere. If you don’t have template, please create one as specified here.
  • VM Initialization Type that can use to VM customization

Participate in Scenarios

  • Information will be provided soon.

See Also

  • Search this documentation for “instance type”, “quantity” or alike to find more information about using the parameter.