# Historically, PD tiers were separated by instance types, which may have been misconfigured.
# This is not a good practice because it causes many duplicated entries. However, it cannot be changed since there is a DB relationship based on the tier name.
# This snippet is a good example of how to group PD tiers by CPU and memory:
#   - component: pd
#     name: 2C4G
#     displayName: 2 vCPU, 4 GiB
#     cpu: 2
#     memoryGi: 4
#     deployType: dedicated
#     tierUnitMap:
#       gcp:
#         - regions: [ us-west1, us-west2 ]
#           tenantIds: [ 0 ]
#           tierUnitKey: gcp:pd:e2-medium:pd-ssd:0:0
#
#       aws:
#         # --- X86 --- #
#         - regions: [ us-west-2, us-east-1 ]
#           tenantIds: [ 0 ]
#           tierUnitKey: aws:pd:t3a.medium:gp3:4000:400
#
#         # --- ARM --- #
#         - regions: [ us-west-2, us-east-1 ]
#           tenantIds: [ 0 ]
#           tierUnitKey: aws:pd:t4g.medium:gp3:4000:400

- component: pd
  name: n1-standard-1
  displayName: n1-standard-1
  cpu: 1
  memoryGi: 4
  deployType: dedicated
  tierUnitMap:
    gcp:
      - regions: [ us-west1 ]
        tenantIds: [ 0 ]
        tierUnitKey: gcp:pd:n1-standard-1:pd-ssd:0:0

- component: pd
  name: e2-medium
  displayName: e2-medium
  cpu: 2
  memoryGi: 4
  deployType: dedicated
  tierUnitMap:
    gcp:
      - regions: [ us-west1, us-west2 ]
        tenantIds: [ 0 ]
        tierUnitKey: gcp:pd:e2-medium:pd-ssd:0:0

- component: pd
  name: t3a.medium
  displayName: t3a.medium
  cpu: 2
  memoryGi: 4
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- X86 --- #
      - regions: [ us-west-2, us-east-1 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:t3a.medium:gp3:4000:400

- component: pd
  name: t4g.medium
  displayName: t4g.medium
  cpu: 2
  memoryGi: 4
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- ARM --- #
      - regions: [ us-west-2, us-east-1 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:t4g.medium:gp3:4000:400

- component: pd
  name: m6g.large
  displayName: m6g.large
  cpu: 2
  memoryGi: 8
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- ARM --- #
      - regions: [ us-west-2, us-east-1 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:m6g.large:gp3:3000:125

- component: pd
  name: n1-standard-2
  displayName: n1-standard-2
  cpu: 2
  memoryGi: 8
  deployType: dedicated
  tierUnitMap:
    gcp:
      - regions: [ us-west1, us-west2 ]
        tenantIds: [ 0 ]
        tierUnitKey: gcp:pd:n1-standard-2:pd-ssd:0:0

- component: pd
  name: m5.large
  displayName: m5.large
  cpu: 2
  memoryGi: 8
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- X86 --- #
      - regions: [ us-east-1, us-west-2, ap-northeast-1, ap-east-1 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:m5.large:gp3:3000:125

- component: pd
  name: c5.xlarge
  displayName: c5.xlarge
  cpu: 4
  memoryGi: 8
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- X86 --- #
      - regions: [ us-east-1, us-west-2 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:c5.xlarge:gp3:4000:400

- component: pd
  name: c6g.xlarge
  displayName: c6g.xlarge
  cpu: 4
  memoryGi: 8
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- ARM --- #
      - regions: [ us-east-1, us-west-2 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:c6g.xlarge:gp3:4000:400

- component: pd
  name: n1-standard-4
  displayName: n1-standard-4
  cpu: 4
  memoryGi: 16
  deployType: dedicated
  tierUnitMap:
    gcp:
      - regions: [ us-west2, us-west1 ]
        tenantIds: [ 0 ]
        tierUnitKey: gcp:pd:n1-standard-4:pd-ssd:0:0

- component: pd
  name: m6g.xlarge
  displayName: m6g.xlarge
  cpu: 4
  memoryGi: 16
  deployType: dedicated
  tierUnitMap:
    aws:
      # --- ARM --- #
      - regions: [ us-west-2, us-east-1, ap-northeast-1, ap-east-1 ]
        tenantIds: [ 0 ]
        tierUnitKey: aws:pd:m6g.xlarge:gp3:4000:400